Im setting up a CUCM8.5 system in the UK. for the most part, things are working well
as not to reinvent the wheel, we decided to use the GBNP (3.1.16). this is not working for some reason.
i am trying to call Australian based numbers 0061xxxxxxxxx
i have created pattern 9.@ and put into a partion call UK-LON-PSTN-PT.
this pattern points to a RL/RG > pointing to a H323 gateway.
the CSS on my phone has access to the partition.
i dial 9 (outside line), then when the first 0 is pressed, i get "your call could not be completed as dialed".
i have setup a test Pattern 9.00! and put in the same partiion as 9.@ and point to the same RL/RG. i can then make these calls without issues.
i have several instances of the 9.@ pattern, all in different partitions (for filtering of certain numbers, with route filters). these all have an "exceed Precidence level" so im sure these are not being hit.
i have enable the following debugging. but nothing is showing up at all, so it appears the call is not exiting the CUCM at all.
I have no other 9.XXXXXXXX patterns at all and have no conflicts that i can see.
also the GBNP is definitely installed and active on the Patterns.
i have setup a cluster in Australia using the same method, e.g. AUNP and using 0.@ and i have no probs at all.
as mentioned, i didnt want to re-invent the wheel and create all the route patterns manually.
i am tempted to try a different version but 3.1.16 should be OK
DNA shows the exact same call flow, when using 9.@ and 9.00!
one thing i did notice, then when i do the DNA on my CCM in Australia, (using the 0.@) i can see my "external Phone mask applied in the DNA output", im not sure why this is not happening on the UK CUCM.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.