On 2010-07-07 21:57, Wen Jun wrote:
> Well, that protection mechanism to avoid surf registration load to SIPX is
> understood. That seems a pretty wise fence.
>
> My another question is how&when SIPX knows to give phones by random
> registration timers ?
It just always randomizes the returned exp
.com]
Sent: Thursday, July 08, 2010 9:23 AM
To: Wen Jun; sipx-users@list.sipfoundry.org
Cc: 'jun,wen'
Subject: RE: [sipx-users] Expires discrepancy of bulk registration by SIPP
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipf
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] On Behalf Of Wen Jun
[jun.wen.s...@gmail.com]
I made 100 subs to initiate registration from SIPP to SIPX with "expires:
300" inside SIP Invite. Whereas, I observed in SI
endpoints vary... when an endpoint or ua is going to expire there is
"generally" a setting that begin to "retry" when "xx" seconds are left on
the registration.
On Wed, Jul 7, 2010 at 8:54 PM, Wen Jun wrote:
>
> Hi, no idea if someone else met the issue of registration expire
> discrepancy. Plea
Hi, no idea if someone else met the issue of registration expire
discrepancy. Please help if you have same experience.
I made 100 subs to initiate registration from SIPP to SIPX with "expires:
300" inside SIP Invite. Whereas, I observed in SIPX the expire timers of all
these 100 subs varies from
