Re: [Sipp-users] "Contact:" usage when working with proxy

[Dmitriy K. <dmi...@co...>]

"next_url" or any custom variable obtained through regex could be used 
for setting up new Request URI or any field in the header. This is very 
useful but not enough for sip proxy testing.
There is no any way so far to customize socket address where to send SIP 
message to. We have:
1) remote_host command line parameter
2) -rsa command line option
But what is really needed - ability to change remote address on the fly 
(in the UAC scenario), for example adding xml attribute to the <send> 
element. For example:

   <send retrans="500" send_to_addr="[next_url]">
     <![CDATA[

       BYE [next_url] SIP/2.0
       Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
...

meaning that remote host address and port to send msg to would be 
extracted from URI specified in xml attribute /scenario/send/@send_to_addr

Dmitriy Kargapolov wrote:
> Hold on a little bit.
> I was not correct about using of "Contact:" field.
> The things are much more tricky about behavior inside a dialog.
> But just for the future it might be convenient to have direct access to 
> the "Contact:" field, with no involving regular expressions...
> Thanks.
> 
> Olivier Jacques wrote:
>>> On 3/30/06, Dmitriy Kargapolov <dmi...@co...> wrote:
>>> Hello,
>>> I tried to test UA behind SIP proxy using default UAC scenario.
>>> It failed because embedded UAC scenario has same address pattern for the
>>> first line if the INVITE, ACK and BYE requests:
>>> sip:[service]@[remote_ip]:[remote_port]
>>> But the UAC should send ACK and BYE to URL fetched from "Contact:" field
>>> of the final response. Even when packet goes physically to the proxy
>>> (which address comes from Record-Route set).
>>>
>>> I didn't find any keyword for fetching / using contacts, so for my test
>>> I just added this small functionality to the latest snapshot. In my
>>> scenario I'm using following address line in ACK and BYE:
>>>       ACK [contact] SIP/2.0
>>>       BYE [contact] SIP/2.0
>>> Patch attached for reference.
>>> Thanks.
>>
>> Folks,
>>
>> from the discussion above:
>> - Is there anything to do on SIPp code?
>> - Does next_url fit your need?
>> - Should I update the default UAC scenario?
>>
>> Thanks to clarify,
>> Olivier.
>> -- 
>> http://www.hp.com/go/opencall/
>>
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live 
> webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Sipp-users mailing list
> Sip...@li...
> https://lists.sourceforge.net/lists/listinfo/sipp-users
>