Problem bearer capability not authorized on forwarding to/from PSTN
We're having problems when users forward calls to the PSTN and the originating caller is also from outside our network (PSTN).
caller 1 (PSTN cell phone) calls into internalcaller (Joe)
Joe's phone set cfwdall to his home number
anyone calling from within the company to joe's phone gets forwarded just fine to his home. caller1, however, calls joe's phone and gets sent seemingly to the provider and back again to us with error in the CDR record 'bearer capability not authorized'.
My hunch is that the original calling party number is somehow being presented to our carrier who is rejecting the call because it does not belong to us.
I'm looking through CallManager and there are so many places for caller id presentation. Here's what I have
route pattern (which matches forwarded number)
Use Calling Party's External Phone Number Mask=false
route list (which would be matched)
route group (which would be matched)
MGCP PRI (which would be matched)
Called party IE number type unknown=CallManager
Calling party IE number type unknown=CallManager
Caller ID DN="' (blank)
Called Party Transformation CSS=<None>
Use Device Pool Called Party Transformation CSS=true
Calling Party Transformation CSS=<None>
Use Device Pool Calling Party Transformation CSS=true
Phone/Line being forwarded
External Phone Mask=actual DN assigned to the phone
Re: Problem bearer capability not authorized on forwarding to/fr
This is a common trouble with newer PRI service that is delivered via IAD that presents PRI to CPE but is SIP on the telco side connected to some soft-switch. Do you know if you have a traditional PRI (i.e. plugged directly into a RJ-48C jack) or a SIP based circuit where you are plugged into an IAD/router of some sort?
First, I would try to get the provider to fix the problem. If they cannot, then someone here should be able to help you work around it by forcing a valid caller ID on forwarded calls for example.
Worst case, the provider should be able to "hard code" a single number for caller ID of all calls from your system. You would lose ability for individual users to have their own caller ID this way though.
-- please remember to rate and mark answered helpful posts --
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...