Hi Subhrojyoti,<br><br>a) Can you compare both NANP files for the changes that were made? What actually they are changing in the NANP which is upsetting?<br>b) Reboot cluster in the right order<br>c) As a temporary solution, you might try registrying gateway(s) to the sub only.<br>
<br>-- <br>Smile, you'll save someone else's day!<br>Frog<br><br><br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Subhrojyoti<br>
> Banerjee<br>
> Sent: Thursday, September 24, 2009 4:20 PM<br>
> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: [cisco-voip] Cannot dial outbound!<br>
><br>
><br>
><br>
> Hi All,<br>
><br>
> We have a CCM 4.1(3)ES66 cluster with 1 PUB and SUB. Currently I have a<br>
> situation where, if phones are registered to SUB they can make OUTBOUND<br>
> calls but when I change the DP and make one of them register to PUB outbound<br>
> calls cannot be made from that IP Phone. It's something like this-<br>
><br>
> DP1- Sub, Pub<br>
> DP2- Pub, Sub<br>
> DN- 89400<br>
> DD- 00620679233<br>
> RP- 0.@<br>
><br>
> When I change the device pool of this IPT to DP1 then we can call outbound,<br>
> but if I change it to DP2 then call fails. No other config changes are made.<br>
> Infact we are not able to dial more than "00". I have checked the CCM trace<br>
> and I see "Digit analysis: potentialMatches=<div id=":8o" class="ii gt">NoPotentialMatchesExist"<br>
> immediately after "00" is dialed. This is strange because the same phone<br>
> with CSS intact is able to make calls when registered to SUB.<br>
><br>
> To give some background on this, about a month or so back, we had the same<br>
> problem, but that time it was with the SUB. Customer claimed that few<br>
> changes (not sure what exactly) were made to the NANP file in the SUB after<br>
> which outbound calls from SUB failed. I had created a RP with full E.164 and<br>
> was able to make outbound call, which made me think probably the NANP macro<br>
> in SUB was corrupt or not invoked. I replaced the backup of the NANP file in<br>
> SUB but it didn't help, even tried copying the one from PUB which also<br>
> didn't help. Infact I tried republishing the DB from PUB using DBLHelper but<br>
> it didn't make any difference either. Ultimately we rebuild the SUB from a 2<br>
> month old RAID 1 disk and then republished the PUB database once again to<br>
> SUB.<br>
><br>
> Things worked just fine until last 2 weeks when again few changes were made<br>
> to the NANP file and dialing from PUB failed. This time, I have tried<br>
> replacing the NANP file in PUB from the SUB but that didn't help. DBLHelper<br>
> doesn't show any DB problem, which was probably expected. Now the only thing<br>
> left is the rebuilding of PUB from the old RAID 1 and then republish it to<br>
> the SUB, offcourse that would mean 2 month old DB.<br>
><br>
> Although I'm yet to check the traces(SDI/SDL) in details, I was wondering if<br>
> anyone has ever faced such an issue and could this be a possible bug?<br>
><br>
> Thanks,<br>
> Subhrojyoti<br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
<br>
<br>
<br>
--<br>
Thanks,<br>
Syed Khalid Ali<br>
</div><br>