Most of Core Service Provider VOIP Platforms supports SIPConnect option 1 and option 2 but they prefer option 2. BroadWorks is one of them. In option 2, we just register with main Id (called Parent ID) and every out going INVITE has Parent Id in 'FROM' header. Option 2 behaves like single endpoint to ISP S/W.
- Vipul Rastogi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Saturday, September 06, 2008 2:27 AM To: [EMAIL PROTECTED]; [email protected] Subject: [Sip-implementors] SipConnect Registration/Authentication Questions Hi, I'm looking to find out some information on how service providers have implemented sipconnect and what Core Service Provider VOIP Platforms support the SipConnect draft currently. I'm curious if anyone has attempted to work around the implied mechanism for bulk registration of the DID's as noted in the sipconnect spec. The spec appears to indicate that the IPPBX should be able to send a single registration with a Master/Main DID and its IP address over the SIP Trunk to the provider, the providers registrar is then meant to have already preconfigured in it a range of DID's which are tied to this received register as the trigger event to register the outstanding range of DID's that will then be routed to this IPPBX that was only required to send up the single register. If the core proxy of the provider isn't capable of having this trigger event and range of numbers to be registered from receiving the single register, is there a means to emulate this function on an SBC or on some intermediary server in the network? Are there particular providers who have this sipconnect functionality supported? Any comments/direction would be appreciated. Thanks, Gene _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
