Asterisk Not Replacing Private FROM Ip With Public IP In INVITE
I’ve split this thread off from another (PJSIP authentication) because I think the root cause is something different. I think the problem is the following FROM line in my SIP INVITE transaction:
From: “MYNAME”
The IP address above is an internal/non-routable IP, so Twilio is rejecting it. For some reason Asterisk is not replacing the private IP with my public IP address. My pjsip.transport.conf contains a stanza for this transport with:
local_net=172.31.0.0/16
Is that all that’s needed for Asterisk to replace the from IP with the external IP? I’m not clear on why Asterisk is not substituting the private FROM ip with a public one…
—
6 thoughts on - Asterisk Not Replacing Private FROM Ip With Public IP In INVITE
type=endpoint rewrite_contact=yes force_rport=yes rtp_symmetric=yes
—
http://help.nyigc.net/
—
You need to put your external IP in the transport configuration:
external_media_address=X.X.X.X
external_signaling_address=X.X.X.X
external_signaling_port=5060
Telecomunicaciones Abiertas de México S.A. de C.V. Carlos Chávez
+52 (55)8116-9161
—
I’ve already done that. However, I used the FQDN instead of an IP address which I think should be ok.
—–Original Message—–
From: asterisk-users [mailto:asterisk-users-bounces@lists.digium.com] Telecomunicaciones Abiertas de México S.A. de C.V. Carlos Chávez
+52 (55)8116-9161
—
I tried that (only needed to add rewrite_contact=yes) but it didn’t help.
BTW, the CONTACT: line holds the correct ip! —
http://help.nyigc.net/
—
Something perhaps noteworth, since this is a multihomed system I bound the transport to 172.31.253.4:5060
I don’t *think* that would cause Asterisk to use that IP in the FROM…at least it shouldn’t.
—–Original Message—–
From: asterisk-users [mailto:asterisk-users-bounces@lists.digium.com] —
http://help.nyigc.net/
—
Copy/paste from FreePBX forum:
It doesn’t touch the From header because it doesn’t matter for normal use. There is a “from_domain” option which can be used to explicitly set the domain portion of the From header. It’s unlikely to be your problem, unless Twilio requires a specific From domain.