[cisco-voip] Cannot dial outbound!
Subhrojyoti Banerjee
subhrojyoti at hotmail.com
Thu Sep 24 16:20:24 EDT 2009
Hi All,
We have a CCM 4.1(3)ES66 cluster with 1 PUB and SUB. Currently I have a situation where, if phones are registered to SUB they can make OUTBOUND calls but when I change the DP and make one of them register to PUB outbound calls cannot be made from that IP Phone. It's something like this-
DP1- Sub, Pub
DP2- Pub, Sub
DN- 89400
DD- 00620679233
RP- 0.@
When I change the device pool of this IPT to DP1 then we can call outbound, but if I change it to DP2 then call fails. No other config changes are made. Infact we are not able to dial more than "00". I have checked the CCM trace and I see "Digit analysis: potentialMatches=NoPotentialMatchesExist" immediately after "00" is dialed. This is strange because the same phone with CSS intact is able to make calls when registered to SUB.
To give some background on this, about a month or so back, we had the same problem, but that time it was with the SUB. Customer claimed that few changes (not sure what exactly) were made to the NANP file in the SUB after which outbound calls from SUB failed. I had created a RP with full E.164 and was able to make outbound call, which made me think probably the NANP macro in SUB was corrupt or not invoked. I replaced the backup of the NANP file in SUB but it didn't help, even tried copying the one from PUB which also didn't help. Infact I tried republishing the DB from PUB using DBLHelper but it didn't make any difference either. Ultimately we rebuild the SUB from a 2 month old RAID 1 disk and then republished the PUB database once again to SUB.
Things worked just fine until last 2 weeks when again few changes were made to the NANP file and dialing from PUB failed. This time, I have tried replacing the NANP file in PUB from the SUB but that didn't help. DBLHelper doesn't show any DB problem, which was probably expected. Now the only thing left is the rebuilding of PUB from the old RAID 1 and then republish it to the SUB, offcourse that would mean 2 month old DB.
Although I'm yet to check the traces(SDI/SDL) in details, I was wondering if anyone has ever faced such an issue and could this be a possible bug?
Thanks,
Subhrojyoti
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090925/bbab716a/attachment.html>
More information about the cisco-voip
mailing list