On Sat, 2009-06-20 at 11:17 -0400, Mark Gertsvolf wrote: > Has anybody ever deployed sipXecs with proxy running on a custom port? > The issues I am encountering with forwardinrules.xml make me think that > I am one of the first to try that. I wonder what other areas in the > product or features might have other unexpected problems.
I did it for a while, but with heavily hand-edited configuration files. The problem in your instance is adjusting the idea of the SIP domain. If the proxy is on host a.b.c listening to port p, then the "SIP domain" is sip:a.b.c:p, and the phone has to generate REGISTERs directed to that URI. The alternative approach is to set up an SRV record that says that sip:u.v.w is serviced by port p at host a.b.c. Then the REGISTER can be directed to sip:u.v.w. The SIP URI sip:a.b.c can't be used, because it doesn't resolve (via RFC 3263) to the host/port that the proxy is listening on. >From what you have said, it looks like forwardingrules.xml is being generated to handle the first form but not the second form. Also, maybe either the x-lite isn't getting configured correctly, or it does not handle non-standard proxy ports correctly. 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 sipXecs IP PBX -- http://www.sipfoundry.org/
