IP Phone stuck in Forward..!!

[xtam1]

Dear All,

I have a weird problem with one of Cisco IP phone 7940 that is registered in CCM 4, the user using this IP phone once made forward to another Cisco IP phone 7940 then he wanted to cancel this forward he is unsuccessful, can anyone help with this problem as I even deleted the 2nd phone and still the 1st phone still forwarding the calls can't stop this forward?!!!

Any help?!!

Regards..

[p.abbeel]

Hi,

Verify the directory number (through Route Plan) which is being forwarded. Check the Call Forward and Pickup Settings.

Note that when a phone is deleted, you need to go towards the Route Plan Report in order to delete the extension also (if wanted) as it is not deleted by default when deleting a phone.

Peter

[MARTIN STREULE]

I had a similar issue a few times (yes, CCM 4.0 too, never with 3.3)

In my case, I already had a "forward" on the phone and expected it to go away when I press "forward" again.

Well, it didn't do that, but provided a dialtone... :-)

Maybe you see the same, it's not clear to me from your description.

I fixed it by stopping / starting the tomcat service on CCM.

(Just a "restart with one click" did not help!)

After that everything was fine again.

Had some strange issues with that and learned (by experience) that order should be publisher - subscriber, ...

Good luck,

Martin

[mcnerney]

I've also seen forwarding issues (either you can't forward the phone or can't unforward the phone) when the subscriber can't access the publisher database, caused by publisher being down or the SQL database is not being replicated. You might want to check the replication of the SQL database: Go to Start>>>Programs>>>>Microsoft SQL Server>>>Enterprise Manager.

[allan.thomas]

Try restarting the DBL component from within the Component Services under Administrative tools. Right click over the DBL component and click stop then start.

I would be inclined to schedule this activity out of hours, depending on the severity of course.

I have come across this previously as known issue in earlier versions of CallManager. However this was affecting IP Phones across the cluster.

If this is not a one off occurence, and is affecting multiple phones, then I would be inclined to search through bug navigator, or open a TAC case.

Hope this helps.

Allan.