[SR-Users] rtpproxy & extra_id_pv

[Marino Mileti]

Hi guys,
I've seen that setting the parameter extra_id_pv, every branch should be hae 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?

[Alex Hermann]

Post by Marino Mileti
Hi guys,
I've seen that setting the parameter extra_id_pv, every branch should be hae

different callid..

Post by Marino Mileti
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?

[Marino Mileti]

Hello,

Post by Alex Hermann

Post by Marino Mileti
Hi guys,
I've seen that setting the parameter extra_id_pv, every branch should
be a different callid..
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?

Post by Alex Hermann
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);

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-***@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


---
Questa e-mail è priva di virus e malware perché è attiva la protezione avast! Antivirus.
http://www.avast.com

[Richard Fuchs]

Post by Marino Mileti
Hello,

Post by Alex Hermann

Post by Marino Mileti
Hi guys,
I've seen that setting the parameter extra_id_pv, every branch should
be a different callid..
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?

Post by Alex Hermann
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
//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.

cheers

[Marino Mileti]

But with from-tag and To-tag it's possible to instruct rtpengine to generate
new couple of ports for each branch of a call? In the source code of
rtpengine it seems that it check only the callid parameter

Post by Marino Mileti
Hi guys,
I've seen that setting the parameter extra_id_pv, every branch
should be a different callid..
modparam("rtpproxy", "extra_id_pv", "$avp(extra_id)")
but in the INVITE message the callid is still the same for all
branches. Any suggest?

Post by Alex Hermann
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.

Post by Marino Mileti
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
//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.

Post by Marino Mileti
cheers

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-***@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


---
Questa e-mail è priva di virus e malware perché è attiva la protezione avast! Antivirus.
http://www.avast.com

[Richard Fuchs]

Post by Marino Mileti
But with from-tag and To-tag it's possible to instruct rtpengine to generate
new couple of ports for each branch of a call? In the source code of
rtpengine it seems that it check only the callid parameter

Yes it will. The call-id is only a vague umbrella under which the
from/to tags are collected. All media parameters, ports etc are
associated with the tags, and a single call can contain any number of
different from/to tags, all with their own separate parameters.

cheers

[Marino Mileti]

Wow! Do you have an example of how to do that? How I have to modify my
kamailio.conf in order to instructs rtpproxy to user from-tag & to-tag in
this way?

-----Messaggio originale-----
Da: sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org
[mailto:sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org] Per conto di Richard Fuchs
Inviato: lunedì 29 settembre 2014 20:21
A: sr-users-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org
Oggetto: Re: [SR-Users] rtpproxy & extra_id_pv

Post by Marino Mileti
But with from-tag and To-tag it's possible to instruct rtpengine to
generate new couple of ports for each branch of a call? In the source
code of rtpengine it seems that it check only the callid parameter

Yes it will. The call-id is only a vague umbrella under which the from/to
tags are collected. All media parameters, ports etc are associated with the
tags, and a single call can contain any number of different from/to tags,
all with their own separate parameters.

cheers

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


---
Questa e-mail è priva di virus e malware perché è attiva la protezione avast! Antivirus.
http://www.avast.com

[Richard Fuchs]

Post by Marino Mileti
Wow! Do you have an example of how to do that? How I have to modify my
kamailio.conf in order to instructs rtpproxy to user from-tag & to-tag in
this way?

You don't have to do anything, tags are already included in all the
messages.

cheers