On Thu, 2009-01-29 at 16:58 +0100, Klaus Darilion wrote: > > Scott Lawrence schrieb: > > On Thu, 2009-01-29 at 15:36 +0100, Johansson Olle E wrote: > >>> Don't use registration. > >>> > >>> Provision the DIDs, then all normal targeting mechanisms work just > >>> fine. > >>> > >>> Someone will say "but what about dynamic addresses" - don't use a > >>> dynamic address for your phone system. > >>> > >> That's a good opinion, but not the reality. There are too many large > >> providers that need a registration and can't place calls on SRV/NAPTR > >> and domains. > > > > Domain names would be a good idea, but they are not required to use > > provisioned connections - you can provision one or more IP addresses > > almost as easily. > > > > Registration was designed to route calls to _a_ contact - it is a > > misapplication of the mechanism to use it for any more than that, and > > that's where the difficulty comes from. > > > > It's a mystery to me why this is so commonly used (yes, I know it is, > > and the sipXecs SIP Trunk support can do it). Why would I want the > > reliability of my inbound calls to be controlled by my system having to > > 'poll' (that's effectively what a registration is) rather than the > > provider just knowing where to send it? > > Hi Scott! > > Yes, static trunk configuration would solve this issue. Nevertheless > there are also IP PBXs behind DNS with dynamic IP addresses, thus > registration should be supported too.
and how many of them do you suppose detect that they got a new IP address with a dhcp refresh and change the registration? how quickly? Putting a high reliability system of any kind on a dynamic address is silly. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
