Dunno. Before you make that conclusion you should see if FS has anything else listening on port 5090 after you made that change. sipx has 5090 in use, but I don;t know about FS.
netstat -l --numeric-ports On Wed, Oct 6, 2010 at 5:12 PM, Dave Redmore <[email protected] > wrote: > Changing the gateway (Freeswitch) to listen on port 5060 fixes the problem. > So, it seems that sipXbridge does not like to use a gateway that uses port > 5090? Is this a bug? Can anyone confirm this? Does anyone care? > > Dave > > ----- Original Message ----- > From: "Dave Redmore" <[email protected]> > To: "Discussion list for users of sipXecs software" < > [email protected]> > Sent: Wednesday, October 6, 2010 1:50:25 PM GMT -06:00 US/Canada Central > Subject: Re: [sipx-users] 500 Internal Server Error on Invite > > Looking a bit more closely at this, I see that sipXbridge listens on port > 5090. I wonder if there is a problem with the fact that my gateway is using > port 5090? I am going to try creating a new Sip Profile in FS to listen on > a different port and see if that helps. > > Dave > > ----- Original Message ----- > From: "Dave Redmore" <[email protected]> > To: "Discussion list for users of sipXecs software" < > [email protected]> > Sent: Wednesday, October 6, 2010 10:58:15 AM GMT -06:00 US/Canada Central > Subject: Re: [sipx-users] 500 Internal Server Error on Invite > > Call trace is attached. > > Looks to me like sipXbridge is getting the call - sees it needs to go to FS > IP/Port (173.15.28.101:5090), but then returns the "500" error. > > Dave > > ----- Original Message ----- > From: "Tony Graziano" <[email protected]> > To: "Discussion list for users of sipXecs software" < > [email protected]> > Sent: Wednesday, October 6, 2010 9:23:01 AM GMT -06:00 US/Canada Central > Subject: Re: [sipx-users] 500 Internal Server Error on Invite > > call trace? pcap wont show what internal logic and signaling sipx is using > inside to come to that conclusion. a trace will. > > On Wed, Oct 6, 2010 at 10:06 AM, Dave Redmore < > [email protected]> wrote: > >> I don't think it is a Freeswitch issue at all. The call never gets past >> sipX. A packet capture on the sipX server shows the Invite come from the >> phone to sipX, sipX returns a "100 Trying" and then immediately returns the >> "500 Internal Server Error" - sipX never tries to reach the Freeswitch box >> in any way - something internal to sipX is dying before it ever gets that >> far. From the error message in the packet capture, it looks like sipX >> chokes when it tries to create the INVITE packet to send on to the gateway >> (Freeswitch). >> >> >> >> Dave >> >> ----- Original Message ----- >> From: "Tony Graziano" <[email protected]> >> To: "Discussion list for users of sipXecs software" < >> [email protected]> >> Sent: Wednesday, October 6, 2010 8:51:30 AM GMT -06:00 US/Canada Central >> Subject: Re: [sipx-users] 500 Internal Server Error on Invite >> >> You really need a call trace to get a chance to see what is being sent >> that generates the "500". >> >> I am not sure why you would be using FS in this way without ensuring that >> FS is rewriting the headers, so I think the issue is going to be "port >> based". I normally do this with a SBC, because they rewrite headers. I am >> not sure if FS does that without a lot of work, they have an example on >> their wiki: >> >> http://wiki.freeswitch.org/wiki/SBC_Setup >> >> On Wed, Oct 6, 2010 at 9:32 AM, Dave Redmore < >> [email protected]> wrote: >> >>> Anyone have any thoughts on this? I'm not sure where to start >>> debugging. Something has tripped up siputilities.java - should I file a bug >>> report? I don't think I am doing anything "wrong" in my config and it >>> doesn't look like a SIP routing/firewall/etc issue. My next step is to >>> rework Freeswitch to listen on 5060 and see if that helps - maybe then is a >>> problem with specifying a different port in the gateway? >>> >>> Dave. >>> >>> ----- Original Message ----- >>> From: "Dave Redmore" <[email protected]> >>> To: "Discussion list for users of sipXecs software" < >>> [email protected]> >>> Sent: Tuesday, October 5, 2010 4:25:38 PM GMT -06:00 US/Canada Central >>> Subject: Re: [sipx-users] 500 Internal Server Error on Invite >>> >>> Freeswitch is not on the LAN - it is on its own Public IP. My goal with >>> this experiment to have my Freeswitch server act as an ITSP using Freeswitch >>> as a Proxy/Registar. >>> >>> Dave >>> >>> ----- Original Message ----- >>> From: "Tony Graziano" <[email protected]> >>> To: [email protected] >>> Sent: Tuesday, October 5, 2010 4:17:13 PM GMT -06:00 US/Canada Central >>> Subject: Re: [sipx-users] 500 Internal Server Error on Invite >>> >>> I would suspect you should not be using sipxbridge at all. >>> >>> You should instead remove that role from sips and remove the trunks. >>> Recreate the trunks as "unmanaged gateways" to FS (if FS is indeed >>> registering to the ITSP). >>> >>> Sipx shouldn't have to register to FS I don't think, just be "allowed" to >>> send it calls, like anything on the lan. >>> >>> ============================ >>> Tony Graziano, Manager >>> Telephone: 434.984.8430 >>> Fax: 434.984.8431 >>> >>> Email: [email protected] >>> >>> LAN/Telephony/Security and Control Systems Helpdesk: >>> Telephone: 434.984.8426 >>> Fax: 434.984.8427 >>> >>> Helpdesk Contract Customers: >>> http://www.myitdepartment.net/gethelp/ >>> >>> ----- Original Message ----- >>> From: [email protected] >>> <[email protected]> >>> To: sipx-users <[email protected]> >>> Sent: Tue Oct 05 17:12:57 2010 >>> Subject: [sipx-users] 500 Internal Server Error on Invite >>> >>> Hi All, >>> >>> >>> I'm doing some experimenting with some different call routing scenarios >>> and >>> have run into an issue. >>> >>> >>> Sipx 4.2.1 installed from ISO with a Polycom 300 and Grandstream GXP2020 >>> phones connected for testing. >>> >>> >>> Having been testing for a while and everything has been working very >>> well. >>> Had my ITSP connected via B2BUA with sipXbridge and incoming/outgoing >>> calls >>> were fine. >>> >>> >>> I changed the SIP Trunk Gateway that was pointing to my ITSP and pointed >>> it >>> to a Freeswitch server that I am running - just to test some ideas. The >>> Freeswitch server has a public IP and listens on port 5090. I have the >>> "Address" and "Port" fields pointing to my Freeswitch IP and 5090 in the >>> main Gateway configuration page and I have "<FS_IP_ADDRESS>:5090>" set >>> under >>> the "ITSP Account" settings of the Gateway. >>> >>> >>> Sipx is registered to my Freeswitch server via sipXbridge. >>> >>> >>> "Long Distance" Dial Plan is enabled and configured to use my Gateway. >>> >>> >>> When I try to place a call from a phone - I get back a "500 Internal >>> Server >>> Error". A packet capture shows that the phone sends an Invite to sipX, >>> sipX >>> returns "100 Trying" and then returns "500 Server Internal Error, with >>> sipfrag". The Message Body of the packet says "Sipfrag" and "Exception >>> Info >>> Unexpected error creating INVITE at Siputilities.java:839" >>> >>> >>> I have googled this error, but not finding any info. >>> >>> >>> Anyone have any ideas? >>> >>> >>> Thanks, >>> >>> >>> Dave Redmore >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >>> _______________________________________________ sipx-users mailing list >>> [email protected] List Archive: >>> http://list.sipfoundry.org/archive/sipx-users/ >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.984.8431 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> Fax: 434.984.8427 >> >> Helpdesk Contract Customers: >> http://www.myitdepartment.net/gethelp/ >> >> Why do mathematicians always confuse Halloween and Christmas? >> Because 31 Oct = 25 Dec. >> >> >> _______________________________________________ sipx-users mailing list >> [email protected] List Archive: >> http://list.sipfoundry.org/archive/sipx-users/ >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > Why do mathematicians always confuse Halloween and Christmas? > Because 31 Oct = 25 Dec. > > > _______________________________________________ sipx-users mailing list > [email protected] List Archive: > http://list.sipfoundry.org/archive/sipx-users/ > > _______________________________________________ sipx-users mailing list > [email protected] List Archive: > http://list.sipfoundry.org/archive/sipx-users/ > > _______________________________________________ sipx-users mailing list > [email protected] List Archive: > http://list.sipfoundry.org/archive/sipx-users/ > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
