similar to: PJSIP configuration question

I am running PJPROJECT 2.3 and Asterisk 13.0.0. I answer the call, about 15 seconds later, vitality hangs up on my cell phone. However, Asterisk is never notified When the OK (for the answer) occurs, the ACK seems to never be accepted. The OK recvd with ACK sent occurs several times. Here are the pjsip.conf settings... [global] type = global debug = yes [transport1] type = transport bind =

I am not sure what you mean by the ful SIP signaling? Here is the trace for the sip.conf which works successfully. Below that, I will include the trace for the pjsip.conf which it seems Vitelity isn't accepting the ACK in response to the OK ---- SIP --- <--- Transmitting SIP request (1004 bytes) to UDP:64.2.142.93:5060 ---> INVITE sip:8005555555 at 64.2.142.93 SIP/2.0 Via: SIP/2.0/UDP

Thanks George. That was the ip address I was given. Unfortunately, my contact at Vitelity is gone for the day so I can?t verify it with him. I added the qualify_frequency as you suggested and it does appear that I have something configured incorrectly?. <--- Transmitting SIP request (483 bytes) to UDP:0.0.19.196:5060 ---> OPTIONS sip:64.2.142.93 at 5060 SIP/2.0 Via: SIP/2.0/UDP

On Wed, Dec 10, 2014 at 1:27 PM, Dan Cropp <dan at amtelco.com> wrote: > 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

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:

I had my screenshots flipped. Is there a way to make sure the Contact field is NOT included in the ACK response to the OK (for the Answer)? PJSIP is including the Contact for the ACK response to the OK. Contact: <sip:1234 at xxx.xxx.xx.xxx:5060> When using the chan_sip, it does not include that field in the ACK response to the OK. (Been a long couple weeks) Have a great day! Dan

Ok, it didn't quite solve everything. There is one slight issue. When I answer the call on my cell phone, Asterisk sees it as answered. I can play audio, send dtmfs, etc and hear it on my phone. However, a short while later, Vitelity tears down that call and Asterisk is never notified about it. I tell Asterisk to hang up the call (via AMI) and it is removed from Asterisk. I gather the

Thank you Joshua. I will make the modifications this morning and give it a try. Have a great day! Dan -----Original Message----- From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Joshua Colp Sent: Wednesday, December 10, 2014 7:27 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] PJSIP

<snip> > > I translated those settings to the following for pjsip.conf... > > [transport1] > type = transport > bind = 0.0.0.0 > protocol = udp > > [outbound.vitelity.net] > type = aor > remove_existing = yes > contact = sip:64.2.142.93 at 5060 This is incorrect. The contact should be: contact = sip:64.2.142.93 It will use a default port of 5060. I

This fixed the problem. Developer before me wrote some code to build up the dial string. Always thought that string appeared off, but it worked so I left it alone. Thanks Joshua and George for helping with this. Have a great day! Dan -----Original Message----- From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Dan Cropp Sent:

Dan Cropp wrote: > I had my screenshots flipped. Is there a way to make sure the Contact field is NOT included in the ACK response to the OK (for the Answer)? > > PJSIP is including the Contact for the ACK response to the OK. > Contact:<sip:1234 at xxx.xxx.xx.xxx:5060> > There is no configuration option to configure this behavior. What is the full SIP signaling? -- Joshua

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). Vitelity doesn?t seem to process it, so they send an OK again. The OK receive, Transmit ACK occurs 4 times. A short while later, Vitelity hangs up

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. One minor detail, we are using ip authentication. When Vitelity changed my account from user based authentication to IP based authentication, they stopped including a user for

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 work we need. From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of

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... [HVout] type=friend dtmfmode=auto host=64.2.142.93 disallow=all allow=ulaw canreinvite=no trustrpid=yes sendrpid=yes nat=yes context=TestApp On Dec 15, 2014, at 9:32 PM, George Joseph <george.joseph at fairview5.com<mailto:george.joseph at

Yes, outbound calls are the only ones I?m trying. From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of George Joseph Sent: Monday, December 15, 2014 4:59 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] PJSIP configuration question On Mon, Dec 15, 2014 at 3:54 PM, Dan Cropp <dan at

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

Hi, all. I'm probably doing Something Dumb(tm), so please feel free to point out whatever I'm missing, no matter how stupid. Anyway, I've got IAX set up to Vitelity. When I try to call my DID, I get: Rejected connect attempt from 64.2.142.19, who was trying to reach '6031234567@' This leads me to my first question -- why doesn't it show a context? (My second is,

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

Hi All- ? I have successfully routed calls into our asterisk system from several DID providers in the USA, but for some reason I'm having a problem getting Vitelity to work. ? We are using the IAX protocol, and the symptom is that only about 50% of the calls terminate properly into my asterisk system - the rest get a busy signal.? The ones that do not come in don't show up at all on