Hi, very grateful if some one can shed hints into my scenario. I am running
SIPp svn 590.
My UAC is talking to UAS through a SIP Register/Proxy. When UAS received the
INVITE from SIP Proxy, the via headers were listed as followings:
Via: SIP/2.0/UDP
192.168.2.6;branch=z9hG4bK-sipapp-08cfafff1cf32f14e2fbdfd1262508a85dce
Via: SIP/2.0/UDP
192.168.2.6;branch=z9hG4bK-sipapp-08cc700bca9b03bc99aafb4ffc9432f4f085~6b297
230d8cf380f65237fe376032c4e
Via: SIP/2.0/UDP 192.168.2.2:47911;branch=z9hG4bK-23688-1-16
When UAS responsed with 180 ring by [last_Via:], the via header was listed
as following:
[truncated] Via: SIP/2.0/UDP
192.168.2.6;branch=z9hG4bK-sipapp-08cfafff1cf32f14e2fbdfd1262508a85dce,
SIP/2.0/UDP
192.168.2.6;branch=z9hG4bK-sipapp-08cc700bca9b03bc99aafb4ffc9432f4f085~6b297
230d8cf380f65237fe376032c4e, SIP/2.0/UDP 192.168
Is it normal or not for the truncated via header ?
While it was strange that my SIP Register/Proxy sent UAS another unexpected
INVITE and that struck my scenario.
Regards,
Jun
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
