If you're using UKNP 27.0 with CallManager 4.X then beware that this may give strange behaviour...
This Dial Plan was released primarily to add 075xx mobile numbers to the list of supported E.164 numbers of the dial plan; but has unfortunately exhibited strange issues with dialling out.
If you experience issues with ISDN Q.931 messages being returned on the gateway with either "No bearer channel available" or "Number not obtainable" then you may find that the dial plan is causing the gateway to send out incorrectly formatted Plan and Type fields. This can be remedied in two ways:
1) Change the "Called Party IE Number Type", "Calling Party IE Number Type" and both Plans under the Outbound Calls settings section of Gateway configuration page of CallManager to "Unknown" instead of "Cisco CallManager".
2) Add the following line to the serial0/0/0:15 interface:
isdn map .* plan unknown type unknown
As far as i'm aware, this patch has now been recalled and Cisco are working on a replacement.
Showing posts with label dialplan. Show all posts
Showing posts with label dialplan. Show all posts
Tuesday, 16 October 2007
Tuesday, 20 February 2007
When the CallManager went Pete Tong...
ARGH.
Well i’m on a customer site and the most bizarre things are happening. Essentially three different engineers have looked at the problem, and spent hours on it, to find that it’s still broken. We found that the Callmanager service was only running on the Subscriber so we kick started this off - but to no avail. Finally after a Publisher restart did the problem go away. However the other site that we added before this one in London is exhibiting the same problem, and wasn’t fixed by the reboot. Very strange…
Essentially it’s a dialling problem to do with picking the right route pattern. Whoever installed the original design in this centralised Callmanager cluster is just an idiot - where logged off phones have the Unrestricted Call search space on them so you can call anywhere from any logged off phone (Toll fraud anyone?), whereas when you log on, that’s where the restrictions come on…
Basically it’s a failed attempt to get the route pattern design correct so that employees can move sites and use the local gateway instead of their own gateway back at ‘home base’ ergo getting cheaper local calls. It’s all a very woolly subject that needs a darn good article writing about it. Watch this space.
Oh and i’m tired of travelling - in London at mo, Scotland Friday. Eurgh.
Well i’m on a customer site and the most bizarre things are happening. Essentially three different engineers have looked at the problem, and spent hours on it, to find that it’s still broken. We found that the Callmanager service was only running on the Subscriber so we kick started this off - but to no avail. Finally after a Publisher restart did the problem go away. However the other site that we added before this one in London is exhibiting the same problem, and wasn’t fixed by the reboot. Very strange…
Essentially it’s a dialling problem to do with picking the right route pattern. Whoever installed the original design in this centralised Callmanager cluster is just an idiot - where logged off phones have the Unrestricted Call search space on them so you can call anywhere from any logged off phone (Toll fraud anyone?), whereas when you log on, that’s where the restrictions come on…
Basically it’s a failed attempt to get the route pattern design correct so that employees can move sites and use the local gateway instead of their own gateway back at ‘home base’ ergo getting cheaper local calls. It’s all a very woolly subject that needs a darn good article writing about it. Watch this space.
Oh and i’m tired of travelling - in London at mo, Scotland Friday. Eurgh.
Subscribe to:
Posts (Atom)
