Yea,
The registration function looks fine. If x-lite doesnt reuse the call ID then it will be treated a completely different registration entry. It shouldn't be a problem if the 2nd registration attempt is being generated near the current registration expiry time. On Sun, Jun 14, 2015 at 2:53 PM, Aqs Younas <[email protected]> wrote: > Sorry for my late reply. > > Yes, second registration is done before expiry time and server does send > expire value of 3600 in 200 ok. Below is my registration code. > > if (is_method("REGISTER")){ > if(!www_authorize("", "subscriber")){ > www_challenge("", "0"); > exit; > } > > if (!save("location")) > sl_reply_error(); > > exit; > } > > I think issue is with x-lite, because when i used zoiper, there was only > one registration. > Thanks for you help. > > > > On 12 June 2015 at 15:23, Tito Cumpen <[email protected]> wrote: > >> Aqs, >> >> >> It looks like these a two separate entries based on the call-id: >> >> >> 76589ZTlhODhlODE3MjY1N2E5ZGJhM2M0MjNjOWM3NDI3ODU >> >> 76589NjY1NjYxNDdjNjBjNjEyYmVjN2JhMDQzYzRjYzVmY2I >> >> Naturally the client should refresh the registration by re-using the call >> id. The server would respond with challenge specifying the attached auth >> header was stale. The UAC would reply with a newly generated auth header. >> Is this second registration attempt being made prior the to registration >> expiry time? is the server sending a 200 ok with an expiry time in the >> contact field? Also can you share your registration function? >> >> >> Thanks, >> Tito >> >> >> On Fri, Jun 12, 2015 at 5:56 PM, Aqs Younas <[email protected]> wrote: >> >>> Thanks for you answer. Below is re-captured packets. >>> >>> Session Initiation Protocol (REGISTER) >>> Message Header >>> Via: SIP/2.0/UDP 192.168.1.5:60513 >>> ;branch=z9hG4bK-524287-1---e033e301133bdc5b;rport >>> Max-Forwards: 70 >>> Contact: <sip:[email protected]:60513 >>> ;rinstance=8e3eef20967b3294> >>> To: <sip:[email protected]> >>> From: <sip:[email protected]>;tag=71dd180b >>> Call-ID: 76589NjY1NjYxNDdjNjBjNjEyYmVjN2JhMDQzYzRjYzVmY2I >>> CSeq: 1 REGISTER >>> Expires: 3600 >>> Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, >>> MESSAGE >>> User-Agent: X-Lite 4.8.4 76589-dcb8bf14-W6.2 >>> Content-Length: 0 >>> >>> Request-Line: REGISTER sip:192.168.1.60 SIP/2.0 >>> Message Header >>> Via: SIP/2.0/UDP 192.168.1.5:60513 >>> ;branch=z9hG4bK-524287-1---b5b9926774d60123;rport >>> Max-Forwards: 70 >>> Contact: <sip:[email protected]:60513 >>> ;rinstance=f9c1973b37048538> >>> To: <sip:[email protected]> >>> From: <sip:[email protected]>;tag=e4ef7105 >>> Call-ID: 76589ZTlhODhlODE3MjY1N2E5ZGJhM2M0MjNjOWM3NDI3ODU >>> CSeq: 1 REGISTER >>> Expires: 3600 >>> Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, >>> MESSAGE >>> User-Agent: X-Lite 4.8.4 76589-dcb8bf14-W6.2 >>> Content-Length: 0 >>> >>> Both result successful registration. >>> >>> On 12 June 2015 at 14:23, Tito Cumpen <[email protected]> wrote: >>> >>>> Do you have an example of the request? Are the call id's matching ? >>>> On Jun 12, 2015 5:21 PM, "Aqs Younas" <[email protected]> wrote: >>>> >>>>> Hi, Users. >>>>> >>>>> I try to register my x-lite phone with opensips that is successfully >>>>> registered.But i see after some time, x-lite sends another register >>>>> request >>>>> and there are two entries for same username in location table. >>>>> >>>>> Username Contact >>>>> 14048002020 sip:[email protected]:61404 >>>>> ;rinstance=7792871469eb2327 >>>>> 14048002020 sip:[email protected]:61404 >>>>> ;rinstance=29fcf1d85b004efe >>>>> >>>>> >>>>> I want, user must be register with different softphone for same >>>>> username. Like second entry could be from zoiper,etc but not from same >>>>> x-lite for 14048002020. >>>>> >>>>> Secondly, when i try to run, ./opensipsctl fifo get_statistics >>>>> accepted_regs >>>>> It gives. >>>>> registrar:accepted_regs:: 3 >>>>> >>>>> But there are only 2 entries in location table. >>>>> >>>>> Please pardon me for my naive question, just started learning this >>>>> amazing thing. >>>>> >>>>> Thanks >>>>> >>>>> >>>>> _______________________________________________ >>>>> Users mailing list >>>>> [email protected] >>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>>> >>>>> >>>> _______________________________________________ >>>> Users mailing list >>>> [email protected] >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>>> >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
