Still no pro but...as i have seen the exact same thing i am proposing:
Under "ITSP Account/Advanced" uncheck "Use default asserted identity"
and leave "Asserted identity" empty...
and/or
sending illegal caller id to ITSP. Change callerid for gateway and clear
caller id for user.
Set called id to your username for the particular gateway account.
Why? Not sure about technical details but...
1. My ITSP did a trace and they got u...@domain.com from me....turned
out they wanted nothing
as identity.
2. My ITSP got my number "031234234" as clip but what they wanted was
my account name "u031234234" as caller id.
Changed these two and it all worked....
*Vänliga Hälsningar/Best Regards*
/Ola Samuelson
/
2010-03-11 17:30, Scott Lawrence skrev:
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 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/
_______________________________________________
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/
