VoIP Mailing List Archives

[dan at amtelco.com]

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@fairview5.com (george.joseph@fairview5.com)> wrote:

[george.joseph at fairv...]

On Mon, Dec 15, 2014 at 9:48 PM, Dan Cropp <dan@amtelco.com (dan@amtelco.com)> wrote:

[dan at amtelco.com]

Thanks George.
I will give it a try.

Have a great day!
Dan


From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of George Joseph
Sent: Monday, December 15, 2014 11:14 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] PJSIP configuration question

I think you can actually specify anything, it just has to be populated with something other than a sub-account username.

[dan at amtelco.com]

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 on my cell phone.

Asterisk is never told the call  is gone.

If I hangup the call from Asterisk side,
Asterisk sends the BYE message.
Vitelity responds with a “SIP/2.0 481 Call leg/transaction does not exist”

Again, the trace indicates the ACK message is missing the Contact header.

Additional note: the network admin is asking why the local_net, external_media_address, and external_signalling_address are needed.  He wrote me…“You should NOT have to know your public IP. The firewall should be doing fixup commands to change the values in the packet”


From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of George Joseph
Sent: Monday, December 15, 2014 11:14 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] PJSIP configuration question

On Mon, Dec 15, 2014 at 9:48 PM, Dan Cropp <dan@amtelco.com (dan@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.

[george.joseph at fairv...]

On Tue, Dec 16, 2014 at 9:00 AM, Dan Cropp <dan@amtelco.com (dan@amtelco.com)> wrote:

[jcolp at digium.com]

Dan Cropp wrote:

[dan at amtelco.com]

Thank you George and Joshua.

"This can cause major problems. I've rarely (if ever) come across an ALG (that's what that is) that didn't break something."

I am contacting the network admin and seeing if he can modify the firewall.

I'm a lifelong programmer. Code and programming, I understand.
When it comes to the network, I'm clueless.
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

[dan at amtelco.com]

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 ALG).

I will run more tests, but here is the pjsip.conf I have.


[global]
type = global
debug = yes

[transport1]
type = transport
bind = 0.0.0.0
protocol = udp

[outbound.vitelity.net]
type = aor
remove_existing = yes
qualify_frequency = 60
contact = sip:outbound.vitelity.net

[outbound.vitelity.net]
type = endpoint
context = TestApp
transport = transport1
aors = outbound.vitelity.net
dtmf_mode = rfc4733
force_rport = yes
rtp_symmetric = yes
rewrite_contact = yes
send_rpid = yes
trust_id_inbound = yes
disallow = all
allow = ulaw
direct_media = no

[outbound.vitelity.net]
type = identify
endpoint = outbound.vitelity.net
match = 64.2.142.93

Have a great day!

Dan

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users

[george.joseph at fairv...]

On Tue, Dec 16, 2014 at 11:45 AM, Dan Cropp <dan@amtelco.com (dan@amtelco.com)> wrote: