[Spce-user] modify header in invite message

Daniel Grotti dgrotti at sipwise.com
Wed Jan 25 04:15:02 EST 2017


Hi,
have you set the correct "outbound_socket" in your peer's preferences ?
Please check this out: 
https://www.sipwise.org/doc/mr5.0.1/spce/ar01s11.html#_extra_sip_sockets


Cheers,

--
Daniel Grotti


On 01/25/2017 08:00 AM, Cedric Le wrote:
> Hi Team,
>
> We have two interface on same Sipwise C5.
> Eth0: 172.16.16.111
> Eth1: 172.16.19.57
>
> Ip peering with ip 172.16.19.10
>
> Sip_ext on Eth1
>
> But when sipC5 sent invite message to peer. It alway sent with from
> header is From: "0901774554" <sip:0901774554 at 172.16.16.111
> <mailto:sip%3A0901774554 at 172.16.16.111>;user=phone>;tag=069E3434-5885D11A000CD8A0-8D10F700'
>
> *
> *
> *May i know how to fix this issue*
>
>
>
> U 2017/01/23 04:47:06.846563 172.16.19.57:5060
> <http://172.16.19.57:5060/> -> 172.16.19.10:5060 <http://172.16.19.10:5060/>
> INVITE sip:01677140640 at 172.16.19.10
> <mailto:sip%3A01677140640 at 172.16.19.10>:5060;transport=udp;user=phone
> SIP/2.0'
> Record-Route:
> <sip:172.16.19.57;r2=on;lr=on;ftag=069E3434-5885D11A000CD8A0-8D10F700;ngcplb=yes>'
> Record-Route:
> <sip:172.16.16.111;r2=on;lr=on;ftag=069E3434-5885D11A000CD8A0-8D10F700;ngcplb=yes>'
> Via: SIP/2.0/UDP
> 172.16.19.57;branch=z9hG4bK0836.74847f233a59b3283d6c65e1ae16eae0.0'
> Via: SIP/2.0/UDP
> 172.16.16.111:5080;received=172.16.16.111;branch=z9hG4bKZEC1xaXT;rport=5080'
> From: "0901774554" <sip:0901774554 at 172.16.16.111
> <mailto:sip%3A0901774554 at 172.16.16.111>;user=phone>;tag=069E3434-5885D11A000CD8A0-8D10F700'
> To: <sip:01677140640 at 172.16.19.10
> <mailto:sip%3A01677140640 at 172.16.19.10>;user=phone>'
> CSeq: 11 INVITE'
> Call-ID: MzM3ODdkYjJiODNjMjFjMjNlZWE0Y2U0Y2ZhMDI2MTQ._b2b-1'
> Max-Forwards: 69'
> Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, MESSAGE, OPTIONS, SUBSCRIBE'
> Supported: replaces, norefersub, extended-refer, X-cisco-serviceuri'
> P-Asserted-Identity: <sip:0901774554 at 172.16.16.111
> <mailto:sip%3A0901774554 at 172.16.16.111>;user=phone>'
> Authorization: Digest username="", realm="172.16.19.10",
> nonce="5885d11aeff9b02a1adddda1a1d561e96ae1d7b4",
> uri="sip:01677140640 at 172.16.19.10:5060;transport=udp;user=phone",
> response="ab75c0d0db068a6b714bb7c50e00d4f7", algorithm=MD5'
> Content-Type: application/sdp'
> Content-Length: 260'
> Contact: <sip:ngcp-lb at 172.16.19.57:5060
> <http://sip:ngcp-lb@172.16.19.57:5060>;ngcpct=7369703a3137322e31362e31362e3131313a35303830>'
> '
> v=0'
> o=Z 0 0 IN IP4 192.168.1.52'
> s=Z'
> c=IN IP4 113.161.65.90'
> t=0 0'
> m=audio 8000 RTP/AVP 3 110 8 0 98 101'
> a=rtpmap:110 speex/8000'
> a=rtpmap:98 iLBC/8000'
> a=fmtp:98 mode=20'
> a=rtpmap:101 teleph
>
> U 2017/01/23 04:47:06.848062 172.16.19.10:5060
> <http://172.16.19.10:5060/> -> 172.16.19.57:5060 <http://172.16.19.57:5060/>
> SIP/2.0 401 Unauthorized'
> From: "0901774554"<sip:0901774554 at 172.16.16.111
> <mailto:sip%3A0901774554 at 172.16.16.111>;user=phone>;tag=069E3434-5885D11A000CD8A0-8D10F700'
> To: <sip:01677140640 at 172.16.19.10
> <mailto:sip%3A01677140640 at 172.16.19.10>;user=phone>;tag=sc1vht1-96cc6f3b49981154'
> Call-ID: MzM3ODdkYjJiODNjMjFjMjNlZWE0Y2U0Y2ZhMDI2MTQ._b2b-1'
> CSeq: 11 INVITE'
> Via: SIP/2.0/UDP
> 172.16.19.57;branch=z9hG4bK0836.74847f233a59b3283d6c65e1ae16eae0.0;received-port=5060'
> Via: SIP/2.0/UDP
> 172.16.16.111:5080;rport=5080;received=172.16.16.111;branch=z9hG4bKZEC1xaXT'
> Contact: <sip:01677140640 at 172.16.19.10:5060
> <http://sip:01677140640@172.16.19.10:5060/>>'
> Record-Route:
> <sip:172.16.19.57;r2=on;ngcplb=yes;ftag=069E3434-5885D11A000CD8A0-8D10F700;lr=on>'
> Record-Route:
> <sip:172.16.16.111;r2=on;ngcplb=yes;ftag=069E3434-5885D11A000CD8A0-8D10F700;lr=on>'
> --
> Thanks and Regard,
> Cedric Le
>
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>



More information about the Spce-user mailing list