Discussion:
Call failed - Forbidden
John Clark
2010-03-11 15:30:50 UTC
Permalink
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)



I am not sure where to start with this. I am under the impression it is
a permissions or dial-plan problem since the gateway is registered and
inbound works, but I am unable to correct the problem. Any direction
would be appreciated. I apologize if this is a duplicate post, I have
researched.



John
Tony Graziano
2010-03-11 16:02:19 UTC
Permalink
Post by John Clark
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)
I am not sure where to start with this. I am under the impression it is a
Post by John Clark
permissions or dial-plan problem since the gateway is registered and inbound
works, but I am unable to correct the problem. Any direction would be
appreciated. I apologize if this is a duplicate post, I have researched.
You need to ask callcentric what you should be sending them. Last time I
played with theirs I had it working in 5 minutes. They expect all outbound
calls (US) to be in this format:

1NPXNXXZZZZ (ex. 14345551212).

You also need to understand they will control your outbound callerid and all
inbound calls will be to your callcentric account number, multiple DID's to
route directly to users will not work with callcentric.

So create a custom dialplan to look for any 10 digits and have it
automatically add the "1" and send it to the callcentric gateway in
"Sytsme>DialPlan". Move that rule above the already active rules and restart
services as prompted. Make sure the rule has LONG DISTANCE permissions and
the user making the call is allowed LONG DISTANCE.

John
Post by John Clark
_______________________________________________
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/
Good luck.
--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: ***@myitdepartment.net

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
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.
Scott Lawrence
2010-03-11 16:30:20 UTC
Permalink
Post by John Clark
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-***@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://
Ola Samuelson
2010-03-11 16:47:07 UTC
Permalink
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 ***@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
/
Post by Scott Lawrence
Post by John Clark
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
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)
_______________________________________________
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/
John Clark
2010-03-11 22:08:20 UTC
Permalink
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:***@avaya.com]
Sent: Thursday, March 11, 2010 10:30 AM
To: John Clark
Cc: sipx-***@list.sipfoundry.org
Subject: Re: [sipx-users] Call failed - Forbidden
Post by John Clark
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-***@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

Loading...