internal IP replaced with public IP, calls fail

lifespeed

Member
Joined
Sep 25, 2010
Messages
287
Reaction score
0
I am trying to use Verizon 4G wireless as a backup to wifi voip. This work marginally on AT&T, with poor voice quality mainly due to their poor network in my area.

Verizon has much better network capacity. However, after much examing of Asterisk CLI logs and Bria for Android logs, I find that Bria sends out a private IP address in via and contact messages. However, what is received by PIAF (purple * 1.8.3) is the public IP address!

How is this happening? It almost sounds like a SIP ALG in a consumer router substituting the public IP. The problem is that something appears to be breaking my VoIP calls using Verizon 4G. Is this likely to be the issue? How can I address it?

I have tried combinations of nonat, force_rport, etc in my extension configuration. I can successfully make SIP URI calls that don't involve my PIAF box, so I know this is possible using VZW network.

Thanks in advance for any insight into what appears to be a network problem.
 
still stumped, surely I am not the only user to run across this (NAT?) problem

Help! I really need to get this to work. I suspect my problem is not an uncommon one, as I find I have a similar problem behind my corporate network.
This is what I know:

1) calls from my LAN wifi and numerous public wifi hotspots work normally.

2) calls from my corporate network wifi work for a short time, and then outgoing audio from Bria for Android fails. Can't hang up the call normally.

3) calls from Verizon 3/4G data network work for a short time, then disconnect or outgoing audio fails. Can't hang up normally.

I have looked at the Asterisk CLI logs and Bria logs. Bria is sending the private IP address behind VZW firewall (Global IP 3G unchecked). Asterisk is receiving public IP for VZW (VZW is running SIP ALG and replacing the IP?). Port numbers appear to be the same.

My guess is this is the cause of the confusion. I think Asterisk would behave better if it received the private IP. It would then know the extension is behind NAT. But it gets the public IP so perhaps defeat the NAT handling?

I am all out of ideas . . . :confused5:

Edit: I have tried all combinations of nat, canreinvite, and qualify settings for the extension. Doesn't seem to make a difference.
 

Members online

No members online now.

Forum statistics

Threads
26,688
Messages
174,412
Members
20,259
Latest member
Fadeek86
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top