Re: CallManager 4.1(3)sr5b

rbpollock01 · ‎08-02-2007

Ever since upgrading to sr5b I have been having weird issue regarding directory numbers being removed. When a directory number is removed it still appears to be in the system. although when you search in route plan report it returns no matches. Database replication appears to be operational. I have also had a number that was removed and when added back would not work in the primary partition. I created a second partition as a work around.

jcvanwyng · ‎08-24-2007

We are having the exact same issue. Ever since I applied sr5b, I have been having replication issues. We are migrating our phones from a traditional PBX to CallManager. We have had several instances where we add a phone to CallManager, then remove it (putting it back on the PBX), and get a fast busy when we dial that number. Also I had a problem adding an MGCP gateway. All this started with sr5b. The only way out of this has been to reboot the servers.

n.warburton · ‎08-24-2007

Just for info, have you been to the route plan report, find Unassigned numbers and also deleted from here too? We are looking at sr5b to install onto a system running sr4 and dont really want this issue too!

jcvanwyng · ‎08-24-2007

I also have checked the Unassigned dial numbers and deleted it out of there. It still seems to be stuck in memory. We currently have a TAC case open.

rbpollock01 · ‎08-24-2007

Please let me know what your findings are.

jcvanwyng · ‎09-07-2007

TAC has instructed us to apply ES123. We will be doing that this weekend.

mrugeshpatel_2 · ‎09-07-2007

can you please send me the ES?

n.warburton · ‎09-09-2007

Hi all,

Let us know what if you think ES123 is a fix. Thanks

jcvanwyng · ‎09-10-2007

We installed it yesterday. It is too early to tell if it fixes this problem. But BEWARE... We had about 400 phones out of 3000 not register to CallManager after putting on this ES. Most our phones are 7941s. The ES contains a device pack. All the phones reset and tried to download new code. Some of them got stuck and had to be manually reset with either a power off or **#**. Big pain.

rbpollock01 · ‎09-11-2007

What was you tac case number my engineer would like to reference it so I can get es123

mrugeshpatel_2 · ‎09-12-2007

606805421

rbpollock01 · ‎08-24-2007

Yes I have even looked in the SQL enterprise manager and can't seem to find it anywhere however callmanager acts as if it exists.

sohaildxbfze · ‎09-10-2007

hi,

in case if u ppl come to know the resolution please let me know,, m also stuck in the same problem

mrugeshpatel_2 · ‎09-10-2007

ES123 fixes it.