similar to: Is it possible to have two endpoints to the same IP address where one uses IP based authentication and the other requires asterisk to register to that system?

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

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 have the following configuration... [aor3] type = aor max_contacts = 1 remove_existing = yes [auth3] type = auth username = 1004 password = SuperSecretProbation [1004] type = endpoint context = IS transport = transport1 auth = auth3 aors = aor3 accountcode = 3 dtmf_mode = rfc4733 device_state_busy_at = 2 force_rport = no moh_passthrough = yes disallow = all allow = ulaw acl = acl1 When a

I am running asterisk 13.1.0 In pjsip.conf, the endpoint section has an aors and an auth field. I can name the auth field anything I want. The key is to set the auth=field accordingly. However, when I try this with the aors field, it never works. It seems I have to name the aors=field to match the name of the endpoint section. Is this correct? Would there ever be a need for multiple aors to

I just realized that you are asking about dynamic AORs, not static Contacts in an AOR. That may be the difference. I have never actually tried giving a dynamic AOR a different name. And you wouldn't want more than one dynamic AOR, you'd just use an AOR that allowed more than 1 contact. On Wed, Apr 1, 2015 at 2:59 PM Trey Hilyard <kctrey at gmail.com> wrote: > I don't know

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.

I am currently running Asterisk 13.1.0-1 I have a chan_sip configuration that works fine with a 3rd party. Third party does not use authentication or registration, it's ip based authentication... When I try switching to PJSIP.conf, I seeing 488 responses from the Asterisk side. What has me really baffled is the debugging indicates [Jul 14 17:28:24] DEBUG[3620] pjsip: sip_endpoint.c

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

Ok Dan, try this... I was able to get this to work behind a NAT and with ip address authentication. [global] type = global debug = yes [transport1] type = transport bind = 0.0.0.0 protocol = udp *local_net=<yourlocalnet I.E. 10.10.10.10/24 <http://10.10.10.10/24>>external_media_address=<your public ip address>external_signaling_address=<your public address>*

Not sure why, but Vitelity changed the settings to IP based authentication on me. Here's the new sip.conf settings they sent me. type=friend dtmfmode=auto host=64.2.142.93 allow=all nat=yes canreinvite=no trustrpid=yes sendrpid=yes When I use these settings to originate calls using the sip.conf they sent me, everything works. Action: Originate ActionID: S8 Channel:

Here's an update... My network admin would not turn off the ALG because it would cause several other problems to other phone systems we have. He looked at the sip trace. What he found is the PJSIP trace showed a different IP address than the older chan_sip so he had me change the aor contact to outbound.vitelity.net At this point, it seems to be working (and this is going through a Cisco

On Mon, Dec 15, 2014 at 2:08 PM, Dan Cropp <dan at amtelco.com> wrote: > > Today, I tried the same behavior on Asterisk 13.1.0 and Asterisk 12.2.0. > > > > Same problem is happening with both of them. > > > > Could this be caused by PJPROJECT 2.3? > > > > Anyone have any suggestions for what I can try? > > > > My boss is giving me until

On Mon, Dec 15, 2014 at 3:54 PM, Dan Cropp <dan at amtelco.com> wrote: > > Yes, everything is behind the same NAT. > > > > For the application I?m working on, the only endpoint is the endpoint to > Vitelity. > > We use AMI to Originate calls from Asterisk endpoint through Vitelity to > phones. > > After that, we control the call through AMI to perform the

On Mon, Dec 15, 2014 at 3:33 PM, Dan Cropp <dan at amtelco.com> wrote: > > Hi George, > > > > Thank you for looking into this. > > This is behind a nat? > > > Just to be clear...both the pbx and local endpoints are behind the same NAT? > [global] > > type = global > > debug = yes > > > > [transport1] > > type = transport

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 =

On Mon, Dec 15, 2014 at 7:34 PM, Dan Cropp <dan at amtelco.com> wrote: > > I am not sure if I entered the correct settings for the transport > information. > > For the local_net, I entered my local ip address, but no mask. I will > check with the network admin so he can verify the settings I entered. > > > You need the network and mask. For example if the ip

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:

Dan Cropp wrote: > I corrected my local_net setting (based on advice from network admin). > > I have tried several different values for the from_user and still have > the same problem. > > Asterisk receives the OK from Vitelity. > > Asterisk sends the ACK (without a Contact header). A Contact header is not required to be in the ACK. > > Vitelity doesn?t seem to

On Mon, Dec 15, 2014 at 9:48 PM, Dan Cropp <dan at amtelco.com> wrote: > > Thanks George. > > I will correct my local_net in the morning. > > Vitelity chan_sip settings I have working, do not have a fromuser. > sip.conf settings... > > I think you can actually specify anything, it just has to be populated with something other than a sub-account username. >

I don't know why you have issues using different names. I have multiple AORs assigned to a single endpoint and it works fine. I have to admit that my AORs do contain the endpoint name, though. For example, for endpoint "myswitch" I have two AORs, "myswitch_1" and "myswitch_2", and I assign them to the endpoint with aors=myswitch_1,myswitch_2. When you say that