search for: identify_by

...k 13.2. I transfer configs from chan_sip to res_pjsip. In chan_sip i have "match_auth_username=yes" and have nothing in pjsip. I have a lot of endpoints and registrations on same SIP server. And it's problem in pjsip now. Is not it? I requesting to add new value for endpoint option identify_by. The value 'uri'. Simple config (cutted): [siptrunk] type=registration transport=udp-transport outbound_auth=siptrunk server_uri=sip:sip.example.com client_uri=sip:1234567890 at sip.example.com retry_interval=60 contact_user=siptrunk-in [siptrunk-in] type=endpoint transport=udp-transport...

...from chan_sip to res_pjsip. > In chan_sip i have "match_auth_username=yes" and have nothing in pjsip. > > I have a lot of endpoints and registrations on same SIP server. And it's > problem in pjsip now. Is not it? > > I requesting to add new value for endpoint option identify_by. The value > 'uri'. > Simple config (cutted): > > [siptrunk] > type=registration > transport=udp-transport > outbound_auth=siptrunk > server_uri=sip:sip.example.comclient_uri=sip:1234567890 at sip.example.com > retry_interval=60 > contact_user=siptrunk-in >...

...ip. >> In chan_sip i have "match_auth_username=yes" and have nothing in pjsip. >> >> I have a lot of endpoints and registrations on same SIP server. And it's >> problem in pjsip now. Is not it? >> >> I requesting to add new value for endpoint option identify_by. The value >> 'uri'. >> Simple config (cutted): >> >> [siptrunk] >> type=registration >> transport=udp-transport >> outbound_auth=siptrunk >> server_uri=sip:sip.example.comclient_uri=sip:1234567890 at sip.example.com >> retry_interval=60...

...p. > In chan_sip i have "match_auth_username=yes" and have nothing in > pjsip. > > I have a lot of endpoints and registrations on same SIP server. > And it's problem in pjsip now. Is not it? > > I requesting to add new value for endpoint option identify_by. The > value 'uri'. > Simple config (cutted): > > [siptrunk] > type=registration > transport=udp-transport > outbound_auth=siptrunk > server_uri=sip:sip.example.com <http://sip.example.com> > client_uri=sip:1234567890 at sip....

I have a trunk set up for the DID from my provider: [my_provider] type=registration outbound_auth=my_provider server_uri=sip:sip.example.com client_uri=sip:my_username at sip.example.com retry_interval=60 [my_provider] type=auth auth_type=userpass password=123456 username=my_username [my_provider] type=aor contact=sip:sip.example.com:5060 [my_provider] type=endpoint context=from-my_provider

...work with an obi202 and google voice. But I can't configure the endpoint. pjsip: [obi202-auth](!) type = auth auth_type = userpass password = <mypass> [obi202-aor](!) type = aor max_contacts = 2 ; ===== endpoints ======== [gv-voice](obi202-endpoint) auth = gv-voice aors = gv-voice identify_by=auth_username ;identify_by=username ; I also tried this. Same result. context = gv-voice [gv-voice](obi202-auth) username = gv-voice [gv-voice](obi202-aor) ############## From the pjsip logging: <--- Received SIP request (798 bytes) from UDP:<obi_ip>:5062 ---> INVITE sip:<g...

...th_type = userpass > > password = <mypass> > > > > [obi202-aor](!) > > type = aor > > max_contacts = 2 > > > > ; ===== endpoints  ======== > > > > [gv-voice](obi202-endpoint) > > auth = gv-voice > > aors = gv-voice > > identify_by=auth_username > > ;identify_by=username ; I also tried this. Same result. > > context = gv-voice > > > > [gv-voice](obi202-auth) > > username = gv-voice > > > > [gv-voice](obi202-aor) > > > > ############## > > > > From the pjsi...

Dear fellow list readers This is the situation: ISDN Devices => Patton ISDN to SIP GW => Asterisk PJSIP The Patton GW resides on a dynamic IP address, so I cannot really use match=ip in the identify section. The Patton does not send a line parameter. The ISDN Devices behind the patton have different MSN and should be able to send them in the From: Header, so the default endpoint

Hi Gang Mitel PBX use 'options' without username to monitor the connection. Therefore Asterisk PJSIP cannot match an unsername against an endpoint and prints a notice on the console. Is there a way to silence this kind of notice? I wonder if identify_by 'header' could solve the issue to match method 'options', but I was not able to find any documentation about this. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlinde...

...m. Existing... [transport1] type = transport bind = 0.0.0.0 protocol = udp [1002] type = aor remove_existing = yes contact = sip:1002 at xxx.xxx.xxx.xxx [1002] type = endpoint context = mycontext transport = transport1 accountcode = 6 dtmf_mode = inband device_state_busy_at = 48 force_rport = no identify_by = username from_user = 1002 disallow = all allow = ulaw acl = acl1 [identify112] type = identify endpoint = 1002 match = 1002 at xxx.xxx.xxx.xxx I setup the registration and the endpoint. [286] type = aor remove_existing = yes contact = sip:286 at xxx.xxx.xxx.xxx qualify_frequency = 60 [auth8]...

...9 even though it's negotiated as ulaw? Why would asterisk change the format to g729 when disallow = all and allow = ulaw are the endpoint settings? [121] type = endpoint context = IS transport = transport1 aors = 121 accountcode = 2 dtmf_mode = inband device_state_busy_at = 96 force_rport = no identify_by = username,ip disallow = all allow = ulaw from_user = 121 acl = acl1 [10/03 11:29:34.240] DEBUG[21414][C-00000226] chan_pjsip.c: Oooh, got a frame with format of g729 on channel 'PJSIP/121-000001d2' when we're sending 'ulaw', switching to match INVITE sip:2197 at XXX.XXX.XXX....

...rization: Digest username="Steve", realm="asterisk", > > [May 24 09:26:13] NOTICE[47903]: res_pjsip/pjsip_distributor.c:676 log_failed_request: > > Request 'REGISTER' from .....' - No matching endpoint found In the endpoint section there is a parameter identify_by (default: "username,ip"). "username" means, the the from-user is used. Use "yealink" or "Steve" for both user names. Using different names for a phone make it just more complicated. You might have to change the phone configuration. > [yealink] > t...

...igest username="Steve", realm="asterisk", [May 24 09:26:13] NOTICE[47903]: res_pjsip/pjsip_distributor.c:676 log_failed_request: Request 'REGISTER' from .....'  - No matching endpoint found block quote end block quote end In the endpoint section there is a parameter identify_by (default: "username,ip"). "username" means, the the from-user is used. Use "yealink" or "Steve" for both user names. Using different names for a phone make it just more complicated. You might have to change the phone configuration. block quote [yealink] typ...

...hem. Existing? [transport1] type = transport bind = 0.0.0.0 protocol = udp [1002] type = aor remove_existing = yes contact = sip:1002 at xxx.xxx.xxx.xxx [1002] type = endpoint context = mycontext transport = transport1 accountcode = 6 dtmf_mode = inband device_state_busy_at = 48 force_rport = no identify_by = username from_user = 1002 disallow = all allow = ulaw acl = acl1 [identify112] type = identify endpoint = 1002 match = 1002 at xxx.xxx.xxx.xxx<mailto:1002 at xxx.xxx.xxx.xxx> Check this first... identify112 probably failed to load because the match parameter can only take an ip address...

Asterisk 13.8 Is CALLERID(all) supposed to wok for pjsip? When I do this: exten => 1234,Set(CALLERID(all)="Jon Doe" <+123456789>) same => n,Dial(PJSIP/phone123, 30) I expect the callerid to be as set, but is always seems to be "phone123", the name of the endpoint. Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL:

...7] type = auth username = didassignedbybluip password = password [didassignedbybluip] type = endpoint context = TestApp transport = transport1 outbound_auth = auth7 aors = BLUIPIN accountcode = 16 dtmf_mode = rfc4733 device_state_busy_at = 2 force_rport = no rtp_symmetric = no rewrite_contact = no identify_by = username outbound_proxy = chi-sbc3-iad.bluip.com trust_id_outbound = yes from_domain = amtelco.com disallow = all allow = ulaw [identify72] type = identify endpoint = didassignedbybluip match = bluipaddress [registration2] type = registration transport = transport1 client_uri = sip:didassignedb...

...ransport1] type = transport bind = 0.0.0.0 protocol = udp [1002] type = aor remove_existing = yes contact = sip:1002 at xxx.xxx.xxx.xxx [1002] type = endpoint context = mycontext transport = transport1 accountcode = 6 dtmf_mode = inband device_state_busy_at = 48 force_rport = no identify_by = username from_user = 1002 disallow = all allow = ulaw acl = acl1 [identify112] type = identify endpoint = 1002 match = 1002 at xxx.xxx.xxx.xxx<mailto:1002 at xxx.xxx.xxx.xxx> Check this first... identify112 probably failed to load because the match parameter can only take an...

I am trying to configure a connection to BluIP. I am able to make incoming calls work. However outgoing calls are not working. For the Outbound Registration, I noticed the contact field is always the internal IP address of my pc instead of mycompany dot com I can Originate (using AMI) to my Vitelity trunk (IP based authentication). However, when I Originate to my BluIP, it is being rejected.

...=invite send_rpid=false pickup_group= sdp_session=Asterisk dtls_verify=No message_context= mailboxes= named_pickup_group= record_on_feature=automixmon dtls_private_key= named_call_group= t38_udptl_maxdatagram=0 media_encryption_optimistic=false aors=DEADDEADBEEF rpid_immediate=false outbound_proxy= identify_by=username inband_progress=false rtp_symmetric=false transport=transport-udp rtp_keepalive=0 t38_udptl_ec=none fax_detect=false t38_udptl_nat=false allow_transfer=true tos_video=0 srtp_tag_32=false timers_min_se=90 call_group= sub_min_expiry=0 100rel=yes direct_media=true rtp_timeout_hold=0 g726_non_...

...al default_from_user causes crash (Reported by Joshua Colp) * ASTERISK-25797 - app_queue: Crash when calling a queue with a member with a forward to an nonexistent extension (Reported by Etienne Lessard) * ASTERISK-26268 - alembic: 'auth_username' not in PJSIP 'identify_by' enum (Reported by Joshua Colp) * ASTERISK-26145 - pjsip: Deadlock with suspend + masquerade + indicate (Reported by Ross Beer) * ASTERISK-26183 - alembic: error when using sqlalchemy version 1.1.0b2 (Reported by Kevin Harwell) * ASTERISK-26280 - DNS lookups can block channel med...