Hello all! I make kamailio1 remotely register to kamailio2.
Here I set K1 modparam("uac", "reg_timer_interval", 15), and expires in uacreg as 30s. Then K1 should refresh registration after 15s. However the callid and from tag of every registration are different, and the Cseq just 10 or 11,never increased.In RFC3261, when UAC want refresh bindings, A UA SHOULD use the same Call-ID for all registrations during a single boot cycle. Is there any way to reuse the callid and fromtag during refresh registration ? Many thanks! And how to make the Cseq become 12 or more?
On 06/21/2014 07:22 AM, nevious wrote:
Hello all! I make kamailio1 remotely register to kamailio2.
Here I set K1 modparam("uac", "reg_timer_interval", 15), and expires in uacreg as 30s. Then K1 should refresh registration after 15s. However the callid and from tag of every registration are different, and the Cseq just 10 or 11,never increased.In RFC3261, when UAC want refresh bindings, A UA SHOULD use the same Call-ID for all registrations during a single boot cycle. Is there any way to reuse the callid and fromtag during refresh registration ? Many thanks! And how to make the Cseq become 12 or more?
There is no option to enable your desired behaviour, if that's what you mean. It would take implementational changes.
On 21/06/14 13:22, nevious wrote:
Hello all! I make kamailio1 remotely register to kamailio2.
Here I set K1 modparam("uac", "reg_timer_interval", 15), and expires in uacreg as 30s. Then K1 should refresh registration after 15s. However the callid and from tag of every registration are different, and the Cseq just 10 or 11,never increased.In RFC3261, when UAC want refresh bindings, A UA SHOULD use the same Call-ID for all registrations during a single boot cycle.
SHOULD is not like MUST, anyhow, can you point the section number inside the RFC?
Cheers, Daniel
Is there any way to reuse the callid and fromtag during refresh registration ? Many thanks! And how to make the Cseq become 12 or more?
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
Thank Godness for your reply!!! In RFC3261, section 10.2.4 Refreshing Bindings.
I've checked the packages of X-lite and Linphone, they act just like what the RFC says. the registration procedure of them like : R+401+R(auth)+200+R(auth)+200+R(auth)+200+...... During registration, call id and from tag are all the same while Cseq increased by 1. Procedure like: callid[A]/fromtag[B]/Cseq[1]+callid[A]/fromtag[B]/Cseq[2]+callid[A]/fromtag[B]/Cseq[3]+callid[A]/fromtag[B]/Cseq[4]......
I'm sorry I care this so much because if kamailio refresh registration with different callid and from tag, the remte proxy will consider it a new registration and delete all dialogs built before.
In ideal circumstances , I'd like kamailio could just re-send the R(auth) with same Cid an Ftag as a refresh registration before expire.
I'm looking for some breakthrough in source code (too hard!!) The only clue I've found is tm [callid.c:137] geneate many callid and some of them are used in register. tm [callid.c:137]: child_init_callid(): DEBUG: callid: '5db5df8f-7541@127.0.0.1' And the tm [uac.c:243] prepare to send register request. tm [uac.c:243]: t_uac_prepare(): DEBUG:tm:t_uac: next_hop=sip:10.103.28.190 So is there any easy way to achieve my goal? could you give me any directions on source code modification? I found tm.c tm [uac.c] tm [callid.c] tm[timer.c] may be have sth. to do with. Anyway, thank you very very much!! Wish kamailio a good future. PS: A silly question, is kamailio named from 'KAMA', is a God represent sex in india. Just kidding, never mind. :-) http://sip-router.1086192.n5.nabble.com/file/n128622/QQ%E5%9B%BE%E7%89%8720140624094608.jpg
-- View this message in context: http://sip-router.1086192.n5.nabble.com/UAC-module-refresh-registration-coul... Sent from the Users mailing list archive at Nabble.com.
I've met a question like this, did you find any ways to reuse the call id and from tag?
-- View this message in context: http://sip-router.1086192.n5.nabble.com/UAC-module-refresh-registration-coul... Sent from the Users mailing list archive at Nabble.com.