Thanks Scott. The tools helped. It was indeed caused by the ITSP not liking the userid which for Callcentric is the caller ID, and has to be the trunk number they assigned the account, and not the DID you may have associated.
I am still having issues connecting and am now getting network failures, but I will research and see if I can work my way through them before posting again. Thanks again. -----Original Message----- From: Scott Lawrence [mailto:[email protected]] Sent: Thursday, March 11, 2010 10:30 AM To: John Clark Cc: [email protected] Subject: Re: [sipx-users] Call failed - Forbidden On Thu, 2010-03-11 at 09:30 -0600, John Clark wrote: > I found one submission from another user having this same issue in the > forums in January, but there was no reply to his enquiry…. > > > > Symptoms and info… > > > > New install. > > Sipxecs 4.0.4, behind NAT router with sipXbridge implemented. > > All checks and tests pass. > > One SIP trunk (gateway) to Callcentric – shows registered in admin > console and on Callcentric site. > > Inbound calls work and route properly > > Internal calls between phones and pbx work properly (testing with > x-lite soft-phone) > > Outbound calls fail with error “forbidden” (as shown on x-lite > display) You need to figure out where the 'forbidden' is coming from. If you look at the SIP 403 response in the logs (I don't know if x-lite let's you see the whole message) you may be able to tell from the Server header. If not, then you'll need to trace the message flow and see what's going wrong. See: http://wiki.sipfoundry.org/display/xecsuserV4r0/Display+SIP+message+flow+using+Sipviewer when you get the trace data, take a look at it using sipviewer and/or post the trace with a description of your configuration (identify components by IP address), what you were doing, and which call in the trace you're talking about (by call-id or frame number in the trace, preferably). If the Forbidden is coming from sipXproxy, then you have a problem with the permissions required by your dial plan and given to your user. If it's coming from your ITSP, then you need to change how sipXbridge is configured (and/or change how the ITSP is provisioned) _______________________________________________ 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/
