What we did was replicating the registrations to the other servers using proprietary extensions. I am clueless its that’s according to any standard but as usually a server farm will consist only of one vendor registrars I don’t thing it’s a big deal. Maybe someone is interested in a draft about this.

 

Security & Co can be handled with the standard SIP toolset.

 

Example message:

 

X-SNOM-REPLICATE sip:192.168.0.44 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.22:5060;branch=z9hG4bK-q01sdzszu4pp
From: <sip:192.168.0.22:5060>;tag=1
To: <sip:192.168.0.44>
Contact: <sip:192.168.0.22:5060>
CSeq: 1206 X-SNOM-REPLICATE
Call-ID: [EMAIL PROTECTED]
Content-Length: 231
Content-Type: text/xml

<?xml version="1.0" ?>
<registration>
<user>jh</user>
<host>intern.snom.de</host>
<call-id>[EMAIL PROTECTED]</call-id>
<expires>0</expires>
</registration>

 

 

 

--

Dr.-Ing. Christian Stredicke

sip:[EMAIL PROTECTED]

 

-----Urspr�ngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Im Auftrag von Kedar Patil
Gesendet: Mittwoch, 4. Dezember 2002 18:31
An: [EMAIL PROTECTED]
Betreff: [Sip-implementors] implications of multiple registrars

 

Hi,

 

Plase consider foll. case for study:

 

We have two or more SIP registrars for domain abc.com.The rgistration info

however is stored only in single database with proper synchronization. All the

SIP UAs in abc.com domain send registration to a proxy, which forwards them

to one of the registrars and thus tries for laod sharing.

 

Do you foresee any adverse implications of having more than one registrars for

a domain?

 

thanks,

= Kedar =

 

Reply via email to