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
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");
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 specify
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:
To:
From: ;tag=71dd180b
Ca
Do you have an example of the request? Are the call id's matching ?
On Jun 12, 2015 5:21 PM, "Aqs Younas" 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
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:14048002020@192.168.1.5:614
