OK, and how do you usually deal with this? I was thinking of putting the Q-value into the "Display Name" field, so when the device registers, I could get it using $fn (reference to display name of 'From' header) and put it directly to the location table in the database...
Kosilov Fedor writes:
OK, and how do you usually deal with this? I was thinking of putting the Q-value into the "Display Name" field, so when the device registers, I could get it using $fn (reference to display name of 'From' header) and put it directly to the location table in the database...
it is possible to use mi command install a contact with q value for an aor, but i have only used it for permanent registrations.
-- juha
Do you mean ul_add? This is not quite what I want to have.. I want everything to work automatically ;). By the way, how do you make permanent registrations?
2010/11/2 Juha Heinanen jh@tutpro.com
Kosilov Fedor writes:
OK, and how do you usually deal with this? I was thinking of putting the Q-value into the "Display Name" field, so when the device registers, I
could
get it using $fn (reference to display name of 'From' header) and put it directly to the location table in the database...
it is possible to use mi command install a contact with q value for an aor, but i have only used it for permanent registrations.
-- juha
Kosilov Fedor writes:
Do you mean ul_add? This is not quite what I want to have.. I want everything to work automatically ;). By the way, how do you make permanent registrations?
either use long expires value or there may be internal usrloc flag that tells that the registration is permanent. you can check source code of the module for that.
-- juha
kamctl is able to do that. The syntax is in the default help iirc.
Regards, Ovidiu Sas
On Tue, Nov 2, 2010 at 2:58 PM, Juha Heinanen jh@tutpro.com wrote:
Kosilov Fedor writes:
Do you mean ul_add? This is not quite what I want to have.. I want everything to work automatically ;). By the way, how do you make permanent registrations?
either use long expires value or there may be internal usrloc flag that tells that the registration is permanent. you can check source code of the module for that.
-- juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Many thanks to everybody for the answers.
2010/11/2 Ovidiu Sas osas@voipembedded.com
kamctl is able to do that. The syntax is in the default help iirc.
Regards, Ovidiu Sas
On Tue, Nov 2, 2010 at 2:58 PM, Juha Heinanen jh@tutpro.com wrote:
Kosilov Fedor writes:
Do you mean ul_add? This is not quite what I want to have.. I want everything to work automatically ;). By the way, how do you make
permanent
registrations?
either use long expires value or there may be internal usrloc flag that tells that the registration is permanent. you can check source code of the module for that.
-- juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
2010/11/2 Kosilov Fedor dangerkoffe@gmail.com:
OK, and how do you usually deal with this? I was thinking of putting the Q-value into the "Display Name" field, so when the device registers, I could get it using $fn (reference to display name of 'From' header) and put it directly to the location table in the database...
Q-value is a Contact param in the REGISTER request.
-
Iñaki Baz Castillo -
Juha Heinanen -
Kosilov Fedor -
Ovidiu Sas