Call forking and q value
219 views
Skip to first unread message
Grygoriy Dobrovolskyy
Jul 10, 2018, 9:12:28 AM7/10/18
to meetecho-janus
Good day, there is a mecanism of call forking in sip, it is based on the q=value, typicly the default value is -1, and the biggest value is 1
It allow a customer to register two or more phones and ring them like in huntgroups, in parallel or one after another, the value is passed in Contact field: example:
Contact: <sip:joh...@sip.domain.com:5060;transport=udp>;expires=3600;q=0.9
Is there any way to make Janus send that q value with Register with the value of my choice ?
Thank you
RFC EXTRACT
*****************************************************************
If more than one Contact is sent in a REGISTER request, the
registering UA intends to associate all of the URIs in these Contact
header field values with the address-of-record present in the To
field. This list can be prioritized with the "q" parameter in the
Contact header field. The "q" parameter indicates a relative
preference for the particular Contact header field value compared to
other bindings for this address-of-record. Section 16.6 describes
how a proxy server uses this preference indication.
******************************************************************
If more than one Contact is sent in a REGISTER request, the
registering UA intends to associate all of the URIs in these Contact
header field values with the address-of-record present in the To
field. This list can be prioritized with the "q" parameter in the
Contact header field. The "q" parameter indicates a relative
preference for the particular Contact header field value compared to
other bindings for this address-of-record. Section 16.6 describes
how a proxy server uses this preference indication.
******************************************************************
******************************************************************
A common ordering mechanism is to use the qvalue parameter of targets
obtained from Contact header fields (see Section 20.10). Targets are
processed from highest qvalue to lowest. Targets with equal qvalues
may be processed in parallel.
******************************************************************
A common ordering mechanism is to use the qvalue parameter of targets
obtained from Contact header fields (see Section 20.10). Targets are
processed from highest qvalue to lowest. Targets with equal qvalues
may be processed in parallel.
******************************************************************
Lorenzo Miniero
Jul 11, 2018, 4:49:03 AM7/11/18
to meetecho-janus
According to the Sofia SIP docs, you have to pass a NUTAG_M_FEATURES tag when calling nua_register:
that is, here:
Not sure about the format to use is, though. You may want to play with the C code and see if it appears that way.
L.
Grygoriy Dobrovolskyy
Jul 12, 2018, 10:08:23 AM7/12/18
to meetecho-janus
Hello, thank you for the solution, it worked.
вторник, 10 июля 2018 г., 15:12:28 UTC+2 пользователь Grygoriy Dobrovolskyy написал:
вторник, 10 июля 2018 г., 15:12:28 UTC+2 пользователь Grygoriy Dobrovolskyy написал:
Reply all
Reply to author
Forward
0 new messages