Good point -- OpenSIPS is a piece I'd like to remove. I did get sipXproxy to start on a different port -- but then I had trouble configuring X-Lite to connect to the proxy on anything other than 5060.
Can I run multiple instances of sipXproxy on the same host, or have the same instance listen on multiple ports? -----Original Message----- From: Scott Lawrence [mailto:[EMAIL PROTECTED] Sent: December 1, 2008 10:39 AM To: Michael LeBlanc Cc: [email protected] Subject: Re: [sipx-users] Trouble dialing in to SipX from PSTN On Mon, 2008-12-01 at 10:01 -0800, Michael LeBlanc wrote: > I figured out where I went wrong. I was pointing the gateway directly at > the SIP Registrar, rather than the SIP Proxy (5060). Once I had the > gateway talking to the SIP Proxy, the autoattendant and extensions with > aliases set to DiDs were found by SipX. > > The complicating factor is that our gateway has to talk to SipX on a > non-standard port, say port 6060, rather than 5060. So I had to set up > OpenSIPS to perform some routing, taking the requests on port 6060, and > relaying them to SipX on 5060 (and rewrite the contact so it was > recognized by SipX). It sounds like you've got workarounds on your workarounds Getting sipXproxy to run on a different port is not a big deal. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
