So are both gateways via the internal SBC? Are they both with the same ITSP? Are they both pointing to port 5080? Do one or both require registration or use static IP's? Are both known to work independently with sipx? Do both ITSP's want calls in the same format (i.e. +1xxxyyyzzzz)?
I've seen some strange ITSP's: 1. Who require a prefix for every dialed number from me 2. Who require me to register. 3. Who require a separate account for each TN. 4. Who can't send me calls on any port other than 5060. 5. Can't handle refer or reinvite. 6. Who have only one tech support guy. 7. Can't handle MOH in any format. My list goes on and on, and it's not pointed at any one ITSP. A lot of people here know that I've been through several ITSP's and I'm happy with the one I use now. I've said this soooo many times... not all ITSP's are created equal. So in asking questions about your ITSP "not_to_be_disparaging", but to seek knowledge about your configuration in the hopes I can be of some assistance. Your call trace might be very helpful, but I think if you could share the answers to the questions in the first paragraph, it would be helpful. On Thu, Nov 5, 2009 at 3:55 PM, Burden, Mike <[email protected]> wrote: > I suspect that my problems were the result either of somehow messing up > the original gateway when I added the new gateway, or simply testing too > soon after restarting services. > > > > I reverted my sipXecs server to the last snapshot made before I added the > new Gateway, and tried again. This time I was extremely careful to make > sure I didn’t change anything except adding a new Gateway and adding the > Gateway to the dialing plan. > > > > I sent profiles, restarted services, and this time the original Gateway > still works. > > > > I’m still trying to figure out why the new Gatway fails (the sipXbridge > returns, “SIP/2.0 404 No record of ITSP. Check configuration”), but now the > dial plan correctly falls through to the original gateway and successfully > places the call. > > > > > > Tony, thanks for pointing me towards the trace utility. That has been ** > AMAZINGLY** helpful! > > > > > > Mike Burden > > Lynk Systems, Inc > > e-mail: [email protected] > > Phone: 616-532-4985 > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Burden, Mike > > *Sent:* Wednesday, November 04, 2009 11:47 AM > *To:* [email protected] > *Subject:* [sipx-users] Multiple gateways? > > > > Good morning, > > > > > > OK, I’m brand new to both IP telephony and sipXecs, so if I’ve done > something dumb, go easy on me. :) > > > > > > I have sipXecs working correctly with a SIP trunk to our ITSP. This > Gateway uses the Internal SBC (sipXbridge-1) as the route. > > > > I want to add a SIP trunk to a second ITSP. I went to Devices -> Gateways > -> Add New Gateway -> SIP Trunk and filled in the information for the new > ITSP, and set up the Dial Plan so that the original Gateway was first, > followed by the Gateway to the new ITSP. The new Gateway also uses > shipXbridge-1 as the route. > > > > After restarting services, outbound calls do not work at all (fast busy.) > > > > I removed the Gateway for the new ITSP from the Dial Plan and restarted > services, but it still didn’t work (still fast busy.) > > > > I removed the new Gateway and restarted services again, and everything > worked again. > > > > > > Where am I going wrong? Shouldn’t the system use the Gateways in the > order I specified in the Dial Plan? > > > > > > > > Mike Burden > > Lynk Systems, Inc > > e-mail: [email protected] > > Phone: 616-532-4985 > > > > > > _______________________________________________ > sipx-users mailing list [email protected] > 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/ > --
_______________________________________________ sipx-users mailing list [email protected] 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/
