Ranga,
At the end of the rope here... I am thoroughly confounded by this.
I created a new sipXecs install and did *nothing* other than run
sipxecs-setup, added one line, one user, and one SIP trunk (which I know
works).
I did not mess with any port settings at all.
Exact same issue.
-- Robert
M. Ranganathan wrote:
On Tue, Dec 1, 2009 at 7:50 PM, Robert B <d...@spudland.com> wrote:
Ranga,
If it is, it's not my doing. I've changed no port numbers or done anything
out of the ordinary other than create Phone profiles and added gateways.
My sipx install is running both registration and proxy servers per the
Server management tab. My DNS-SRV records are accurate and point to port
5060. Bria is able to register and access the voicemail system without any
issue.
All I can think of is that SipXbridge has been misconfigured. Check
the ports carefully. If, for example you have the ITSP facing port and
the "local port" swapped, then ITSP requests will arrive at your local
port . If you have your NAT forwarding ITSP requests to the local port
then that will cause the same effect. sipxbridge sees a request on
port 5080 (default). It checks to see if that request came from the
sipx proxy. If not an error is generated. This is the effect that you
are seeing.
Ranga
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
