[SR-Users] rtpproxy & extra_id_pv

Richard Fuchs rfuchs at sipwise.com
Mon Sep 29 19:21:06 CEST 2014

On 09/26/14 16:57, Marino Mileti wrote:
> Hello,
>> On Friday 26 September 2014 16:44:44 Marino Mileti wrote:
>>> Hi guys,
>>> I've seen that setting the parameter extra_id_pv, every branch should 
>>> be a different callid..
>>> How can i set this parameter? I've tried with :
>>> modparam("rtpproxy", "extra_id_pv", "$avp(extra_id)")
>>> but in the INVITE message the callid is still the same for all 
>>> branches. Any suggest?
>> Did you assign a value to $avp(extra) in the script, before calling any of
> the rtpproxy functions?
>> Did you use the 'b' parameter in the call to rtpproxy_*() functions?
>> --
>> Alex Hermann
> Yes, i've assigned a value in the script, just to try I've assigned $rU and
> on the log of rtpengine I can see the value of "via-branch" valorized
> correctly. I've also used the 'd' parameter in rtpproxy_manage() function.
> I've also checked on the source code of rtpengine and the part regarding the
> "parse & get" of via-branch value is commented...I'm using the master branch
> of rtpengine.
> This is the piece of code of call_interfaces.c where the via-branch
> parameter is commented:
> //bencode_dictionary_get_str(input, "via-branch", &viabranch);

The via-branch is currently unused in rtpengine, even though it does
appear in the control messages. From-tag and to-tag are sufficient to
identify a unique dialogue within a call.


More information about the sr-users mailing list