Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
521
Views
0
Helpful
13
Replies

CallManager 4.1(3)sr5b

rbpollock01
Level 1
Level 1

‎08-02-2007 10:42 AM - edited ‎03-14-2019 10:54 PM

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.

Labels:
0 Helpful
13 Replies 13

jcvanwyng
Level 1
Level 1

‎08-24-2007 04:56 AM

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.

0 Helpful

n.warburton
Level 1
Level 1
In response to jcvanwyng

‎08-24-2007 06:59 AM

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!

0 Helpful

jcvanwyng
Level 1
Level 1
In response to n.warburton

‎08-24-2007 11:16 AM

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.

0 Helpful

rbpollock01
Level 1
Level 1
In response to jcvanwyng

‎08-24-2007 08:58 PM

Please let me know what your findings are.

0 Helpful

jcvanwyng
Level 1
Level 1
In response to rbpollock01

‎09-07-2007 01:03 PM

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

0 Helpful

mrugeshpatel_2
Level 1
Level 1
In response to jcvanwyng

‎09-07-2007 03:46 PM

can you please send me the ES?

0 Helpful

n.warburton
Level 1
Level 1
In response to mrugeshpatel_2

‎09-09-2007 11:37 PM

Hi all,

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

0 Helpful

jcvanwyng
Level 1
Level 1
In response to n.warburton

‎09-10-2007 11:31 AM

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.

0 Helpful

rbpollock01
Level 1
Level 1
In response to jcvanwyng

‎09-11-2007 05:20 PM

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

0 Helpful

mrugeshpatel_2
Level 1
Level 1
In response to rbpollock01

‎09-12-2007 07:04 AM

606805421

0 Helpful

rbpollock01
Level 1
Level 1

‎08-24-2007 09:07 AM

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.

0 Helpful

sohaildxbfze
Level 1
Level 1

‎09-10-2007 12:58 PM

hi,

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

0 Helpful

mrugeshpatel_2
Level 1
Level 1
In response to sohaildxbfze

‎09-10-2007 01:08 PM

ES123 fixes it.

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents