I seem to recall early on with sipxbridge that if you had multiple gateways pointed to the same IP address, that it created problems. Not like this, but that they were treated like one trunk group. This may have been cleared up in a later release, I don't recall seeing any more discussion of it, however that discussion caused me to create a workaround an installation during that timeframe.
I can state that I have one site that uses the same ITSP for three different accounts, resulting in three different gateways. However, I have each one routed to a different IP address at the ITSP. Gateway one - xxx.xxx.xxx.1 Gateway two - xxx.xxx.xxx.2 Gateway three - xxx.xxx.xxx.3 It works, there are no issues in this specific design and implementation. You might want to check to see if your ITSP can accommodate that for you. From: [email protected] [mailto:[email protected]] On Behalf Of Tony Graziano Sent: Friday, August 20, 2010 12:21 AM To: Jesse Reynolds Cc: [email protected] users Subject: Re: [sipx-users] loop detected in sipxbridge after adding second ITSP to the internal SBC There should be no reason that I can think of that this would not work.I saw one last week with 5 or 6 registrations to the same itsp. What version of sipx is it? On Fri, Aug 20, 2010 at 1:04 AM, Jesse Reynolds <[email protected]> wrote: Hello I have sipxecs behind a pfsense router doing NAT. I had one ITSP account on it with a 100 number range working well. I've just added a second gateway with a second ITSP account to the system. They are both using the same bridge - 'internal SBC'. They are also both using the same ITSP - Internode Nodephone (who run a broadworks system). As soon as I added the second gateway and ITSP account the first one stopped working, and the second doesn't work either. Incoming calls are received and initially ring an extension however the caller gets a rejection. Subsequent calls are rejected. Looking at the logs, something appears to be looping as there's a lot of "482 Loop detected" messages. Even after hanging up both ends there is still this 'loop detected' message being written to the sipxbridge.log file over and over. When I look at the UI - Diagnostics / Internal SBC Statistics, most of the time the two SIP trunks have a registration status of "AUTHENTICATING", with brief periods of "AUTHENTICATED". Is this a limitation of sipx? That I can't connect to two SIP accounts at the same ITSP from the same server? We have an Epygi IP PBX at a different site that is happily registering with two different SIP accounts both at Internode, so this can work. Thank you Jesse Jesse Reynolds Virtual Artists Pty Ltd - http://www.va.com.au/ Phone: 08 7120 7134 (Adelaide) or 02 9043 2288 (Sydney) Mobile: 0414 669 790 _______________________________________________ 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/
