On Fri, Jan 16, 2009 at 6:31 PM, Matsuoka Noriko <[email protected]>wrote:
> Hello, mayama
>
> Thank you for you advice.
>
> >I didn't understand the problem.
> I think my explanation was too bad ! What I wanted to do is, get all
> Record-Route header and keep it in variable or something,
> and paste it in later message.
>
> I think you suggested case was suit my purpose, I check it out.
>
Hello, if you just want to inject the Record-Route headers, you can just use
[last-Record-Route] as below:
<recv request="INVITE" crlf="true" >
</recv>
<send retrans="500">
<![CDATA[
SIP/2.0 200 OK
[last_To:];tag=[pid]SIPpTag01[call_number]
[last_From:]
[last_Call-ID:]
[last_CSeq:]
Contact: Excel<sip:ex...@[local_ip]:[local_port]>
[last_Record-Route:]
Supported: timer
Session-Expires: 21600; refresher=uas
[last_Via:]
User-Agent: Excel_CSP/83.10.226
Content-Type: application/sdp
Content-Length: [len]
...Some SDP ....
]]>
</send>
The only catch is that [last-Record-Route:] always combines all headers in a
single one. For example, if in the INVITE the headers came as:
Record-Route: <sip:64.34.162.221;lr=on;ftag=as570b93cc>
Record-Route: <sip:63.34.162.221;lr=on;ftag=bs570b93cc>
Record-Route: <sip:62.34.162.221;lr=on;ftag=cs570b93cc>
then [last-Record-Route:] will result in:
Record-Route: <sip:64.34.162.221;lr=on;ftag=as570b93cc>,
<sip:63.34.162.221;lr=on;ftag=bs570b93cc>,
<sip:62.34.162.221;lr=on;ftag=cs570b93cc>
This is perfectly valid and equivalent to the former, but if you do want to
send the Record-Route exactly as received, then you can use regex to store
them separately as explained in that thread.
regards,
mayama
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
