Is that my regrexp correct on this situation ? I will try later.
Thanks and Regards,
Jun
<ereg regexp="".*"" search_in="hdr" header="Via"
occurrence="1" assign_to="1" />
<ereg regexp="".*"" search_in="hdr" header="Via"
occurrence="2" assign_to="2" />
<ereg regexp="".*"" search_in="hdr" header="Via"
occurrence="3" assign_to="3" />
_____
From: Evgeny Miloslavsky [mailto:emiloslav...@juniper.net]
Sent: Wednesday, December 02, 2009 5:06 PM
To: Wen Jun
Cc: sipp-users@lists.sourceforge.net
Subject: Re: [Sipp-users] [truncated] Via Header
If you want to be 100% sure I would suggest you to assign first Via header
value to variable "1" , second Via header value to variable "2" and so on.
To distinguish between first second and third Via's within request received
use "occurrence" option.
While sending 180 response put 3 Via headers. That is: Via: [$1]
Via: [$2]
Via: [$3]
This way you'll ensure that outgoing response will have exactly the same Via
headers with exactly the same order as they appeared at request being
responded.
Regards,
Evgeny Miloslavsky
Systest Engineer
Juniper Networks Solutions Israel LTD.
Office: 972-9-9712355
Office: 972-74-7170072
_____
From: Wen Jun [mailto:jun.wen.s...@gmail.com]
Sent: Wednesday, December 02, 2009 10:30 AM
To: sipp-users@lists.sourceforge.net
Subject: [Sipp-users] [truncated] Via Header
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
