On Thu, 2009-04-02 at 13:03 -0500, Tony Graziano wrote: > I'm trying to understand the current method used to send a register > request. > > What I think i'd like to see long term is a 2nd ip address bound > simply to the remote register function, and see the register requests > forward to that (private) ip and allow the traffic between trunking > and remote users become better segregated at some point in the future. > I would think that the second address scheme would also lend itself to > being able to blend it into HA more easily. > > Does this make sense to anyone else?
The method used to send a register request is rather tightly specified. Also, remember that it is done by the *phone*, under direction of the DNS records that it can see, so we Gods of sipX (TM) don't have that much control over the process. The REGISTER request must be constructed with the request-URI of "sip:<whatever your SIP domain is>". That domain will be looked up for SRV, CNAME, and A records (and possibly NAPTR records). The result will be a list of IP addresses (and ports), ordered by priority and between addresses of the same priority, a "weight" telling what fraction of the traffic is to be sent to each one. Those IP addresses/ports are where the phone sends the REGISTER request. This is specified in complete detail in RFC 3263. (Many phones allow specifying an alternative URI as the "outbound proxy", in which case the outbound proxy URI is looked up, rather than the SIP domain.) What is it you're trying to accomplish? What is the overall system configuration you are contemplating? Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
