search for: identify_bi

Hello. Asterisk 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]

On Fri, Mar 6, 2015 at 2:06 PM, Dmitriy Serov <serov.d.p at gmail.com> wrote: > Hello. > > Asterisk 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

On Fri, Mar 6, 2015 at 3:46 PM, Dmitriy Serov <serov.d.p at gmail.com> wrote: > 07.03.2015 0:24, Kevin Harwell ?????: > > On Fri, Mar 6, 2015 at 2:06 PM, Dmitriy Serov <serov.d.p at gmail.com> > wrote: > >> Hello. >> >> Asterisk 13.2. >> I transfer configs from chan_sip to res_pjsip. >> In chan_sip i have

07.03.2015 0:24, Kevin Harwell ?????: > On Fri, Mar 6, 2015 at 2:06 PM, Dmitriy Serov <serov.d.p at gmail.com > <mailto:serov.d.p at gmail.com>> wrote: > > Hello. > > Asterisk 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

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

I'm trying to set up pjsip to 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

On Sat, Apr 6, 2019, at 10:04 AM, sean darcy wrote: > On 4/5/19 10:36 AM, sean darcy wrote: > > I'm trying to set up pjsip to work with an obi202 and google voice. But > > I can't configure the endpoint. > > > > pjsip: > > > > [obi202-auth](!) > > type = auth > > auth_type = userpass > > password = <mypass> > > >

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.

Currently using PJSIP. First, they want me to get this working with the existing PJSIP configuration, but then setup a second box using chan_sip performing similar work. For PJSIP... I currently have an endpoint configured to a system using IP based authentication. It is configured with a match setting in the endpoint section. All channels coming from that IP address go to this endpoint. They

The PJSIP endpoint is configured for ulaw only. Not sure how or why we are seeing the g729 on calls for this endpoint. Would this be a case that asterisk detects the rtp stream is g729 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

Am Wed, May 24, 2023 at 09:40:18AM -0400 schrieb Steve Matzura: > > On 5/24/2023 7:49 AM, Stefan Tichy wrote: > > Am Tue, May 23, 2023 at 07:22:22PM -0400 schrieb Steve Matzura: > > > > > 1. Still can't register my phone > > > The username and password are correct. I don't know what else to try. > > You can start a sip trace from the asterisk

This was supposed to go to the list. I am now thoroughly confused. In the [voipms] stanza where endpoint is defined (type=endpoint), everything points to voipms. But in the [yealink] stanzas, I tried pointing everything to Steve, one item at a time, then both of them, and nothing changed. On 5/24/2023 10:00 AM, Stefan Tichy wrote: block quote Am Wed, May 24, 2023 at 09:40:18AM -0400 schrieb

Thanks George I originally didn?t have the 1002@ for the identify. Changed that when things were not working. I changed it back. Unfortunately, the system I am connecting with doesn?t seem to support the line support. Looking at the SIP packets, I see Asterisk send it. Unfortunately, they do not send the line information as part of the INVITE. I checked with some developers of that system

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:

Thank you Joshua. I tried setting the from_domain for the endpoint, but it still sends the internal ip address for the INVITE's From field [acl1] type = acl deny = 0.0.0.0/0.0.0.0 permit = variousaddress permit = bluipaddress [transport1] type = transport bind = 0.0.0.0 protocol = udp [BLUIPIN] type = aor remove_existing = yes contact = sip:bluipaddress [auth7] type = auth username =

Thank you George. I will pass along the rfc information to those responsible for the other switch. I missed the match_header addition to Asterisk. Unfortunately, the only header field that seems appropriate is the To header. On a separate box I am now trying to configure the endpoint recognition. Planning on multiple endpoints to the same switch, so I am trying to use the match_header field.

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.

On 1 July 2016 at 17:41, Joshua Colp <jcolp at digium.com> wrote: > > >> exten => 1234,Set(CALLERID(all)="Jon Doe" <+123456789>) >> same => n,Dial(PJSIP/phone123, 30) >> > > Your exten line has no priority, is that how it is in your dialplan? > Actually no, I stole that line from an earlier email to this list. Mine has a priority.

The Asterisk Development Team has announced the release of Asterisk 13.12.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 13.12.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following are the issues resolved in this release: New