[Users] ruri, dset, branches ...

[Daniel-Constantin Mierla]

Hello,

On 08/22/05 10:41, Klaus Darilion wrote:

> Hi Daniel!
>
> Thanks for clarifications - one question left. I want to log all 
> destinations of a forked call, but not only the R-URI of these SIP 
> messages, but also the addresses to which the messages are sent (the 
> received paramter), Maybe we can update the $ds variable to also show 
> the received parameter if available, e.g.:
>
> destination set: $ds=Contact: sip:klaus at 83.136.33.19:5060, 
> sip:klaus at 10.10.0.50:8718 (received:publicIP:port)

ok, I will introduce another pseudo-variable to print the complete list 
of destination addresses (similar as for branches). The question is what 
to print if a branch has no dst_uri, empty string between comma? So one 
can match branch addresses and destinations?!?

Regards,
Daniel

>
> regards
> klaus
>
> Daniel-Constantin Mierla wrote:
>
>> Hello,
>>
>>
>> On 08/18/05 15:15, Klaus Darilion wrote:
>>
>>> Daniel-Constantin Mierla wrote:
>>>
>>>> Looking at this issue, I am wondering if worth to add the
>>>> pseudovariables $dh and $dp for destination host and port ... Also I
>>>> am considering to change a bit the $du reference so when the dst_uri
>>>> is not set to point to request URI. Would be these changes usefully?
>>>
>>>
>>>
>>>
>>> Hi Daniel!
>>>
>>> This reveals another question: What is the difference between: 
>>> request URI, first branch, all branches, destionation sets .....
>>>
>>> I used xlog to log all this pseude variables just before t_relay.
>>>
>>>   first branch:    $br=sip:klaus at 10.10.0.50:8718
>>>   all branches:    $bR=sip:klaus at 10.10.0.50:8718
>>>   destination set: $ds=Contact: sip:klaus at 83.136.33.19:5060, 
>>> sip:klaus at 10.10.0.50:8718
>>>   destination uri: $du=<null>
>>>   request uri:     $ru=sip:klaus at 83.136.33.19:5060
>>>
>>> In the above call scenario, there is just lookup() which reveals 2 
>>> contacts, one with public IP and one with NATed IP (received 
>>> structure used).
>>>
>>> Can you please describe the difference of these variables?
>>
>>
>>
>> - a branch is an address other than R-URI that should replace R-URI 
>> in the message in case of parallel or serial forking
>> - all branches pseudo-variables is a comma separated list of the 
>> branches set for the message
>> - destination set is the list of all addresses that will be set as 
>> R-URI for the SIP message (case of serial or parallel forking). This 
>> includes the R-URI and branches.
>> - destination uri is the address where the message is to be sent (the 
>> outbound proxy, next hop -- if it is not set, then the message is 
>> sent based on R-URI address). Note that for each branch you can have 
>> a uri to put as R-URI and an address as dst_uri
>> - request uri is the address in the first line of a SIP request, 
>> after the SIP method ( ;-) )
>>
>>>
>>> - Why does the destination set contains the NATed IP instead of the 
>>> received-IP?
>>
>>
>>
>> Because many SIP UA clients drop the requests that have in R-URI a 
>> foreign address (not the local one on which it listens)
>>
>>>
>>> - Why does all branches only shows the first one?
>>
>>
>>
>> In your case, you have just one.
>>
>>> - Why is the request URI different to the first branch?
>>
>>
>>
>> That's how ser was designed, the branch is set only in case of forking.
>>
>> Daniel
>>
>>>
>>> regards
>>> klaus
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at openser.org
>>> http://openser.org/cgi-bin/mailman/listinfo/users
>>>
>>
>>
>
>