Currently the carrier gets the invite from our public address, and they are responding with a 401 but they say we need to check the NAT so it is not masking the contact and via headers in the register.
In the registration (contact/via) below it is sending the B1 interface IP instead of the public IP. How can this be modified?
REGISTER sip:voip.centurylink.com SIP/2.0
From: <sip:xxxxxxxxxx@voip.centurylink.com>;tag=166a757a6479
To: <sip:xxxxxxxxxx@voip.centurylink.com>
CSeq: 23 REGISTER
Call-ID: d68d1b63a72d9b5a437a592a2d041fba167a6a5e46d1703b0bd45453f3c10a1
Contact: <sip:xxxxxxxxxx@10.5.64.203[/highlight]:5060;transport=udp>
Max-Forwards: 69
Via: SIP/2.0/UDP 10.5.64.203:5060;branch=z9hG4bK-s1632-000433175412-1--s1632-
P-Asserted-Identity: sip:xxxxxxxxxx@voip.centurylink.com
Content-Length: 0
In the registration (contact/via) below it is sending the B1 interface IP instead of the public IP. How can this be modified?
REGISTER sip:voip.centurylink.com SIP/2.0
From: <sip:xxxxxxxxxx@voip.centurylink.com>;tag=166a757a6479
To: <sip:xxxxxxxxxx@voip.centurylink.com>
CSeq: 23 REGISTER
Call-ID: d68d1b63a72d9b5a437a592a2d041fba167a6a5e46d1703b0bd45453f3c10a1
Contact: <sip:xxxxxxxxxx@10.5.64.203[/highlight]:5060;transport=udp>
Max-Forwards: 69
Via: SIP/2.0/UDP 10.5.64.203:5060;branch=z9hG4bK-s1632-000433175412-1--s1632-
P-Asserted-Identity: sip:xxxxxxxxxx@voip.centurylink.com
Content-Length: 0