[SIPForum-discussion] Registrar forcer re-registration

[Mark Holloway]

Depending on where the outage resides and whether you have geographically
diverse SBC's, your gateways should have the ability to point to two
different geographically located SBC's as primary/secondary or use DNS SRV's
with multiple A records.  If you only have one geographic location with an
SBC, the SBC should be configured to monitor your routing and application
server clusters on the protected side of the network so it can forward the
SIP invites to the active servers in the cluster where the users' SIP
registration lives.   

  

 

From: discussion-bounces at sipforum.org
[mailto:discussion-bounces at sipforum.org] On Behalf Of Tyler Parkin
Sent: Wednesday, January 16, 2008 5:40 PM
To: discussion at sipforum.org
Subject: [SIPForum-discussion] Registrar forcer re-registration

 

Good evening,

 

I'm curious to know if there is a SIP method for a registrar to force (an
early) re-registration. 

 

Our network is pretty standard:

 

SIP UA -> SBC -> REGISTRAR

 

In an effort to minimize the effects of an outage event, identifying a
solution for SIP -> PSTN calls is easy.  However, PSTN to SIP calls is more
difficult unless the registration cache in both the SBC and the
Registrar/feature server are updated (due to endpoint IP NAT'ing).  To date,
our only solution has been to re-register the UA's, either via a SIP method
(preferred) or a script that logs into each UA and tears down the endpoint
and rebuilds it.

 

In reading the RFC's, I've been unable to find a SIP method that will force
a UA to re-register prior to reaching the normal expires value and thought
I'd bounce it off the community.

 

Thanks,

 

Tyler

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20080116/f49ce727/attachment-0002.html>