[cisco-voip] extension mobility stopped working

[Wes Sisk]

Wow, you should upgrade.  5.1 is just bad code.  5.1(3) is the bare 
minimum for a production environment and even that is questionable.

To get back online in the near term reboot the cluster, especially the 
publisher.

Most likely candidates (covered before on this list):
CSCso93220    dbnotify client removed, unable to reset phones
CSCsq95431    Notify client removal is causing mwi not to work

/Wes


On Wednesday, May 06, 2009 2:53:41 PM, Darren Ducote 
<ducotedt at stfran.com> wrote:
>
> Call manager 5.1.2.......cisco is having me bounce the Tomcat service, 
> but it doesn't seem to be working. Should I try that next?
>
>  
>
> ------------------------------------------------------------------------
>
> *From:* Tanner Ezell [mailto:tanner.ezell at gmail.com]
> *Sent:* Wednesday, May 06, 2009 1:45 PM
> *To:* Darren Ducote
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] extension mobility stopped working
>
>  
>
> What version of CCM/CUCM? did you try restarting the EM service?
>
> On Wed, May 6, 2009 at 10:44 AM, Darren Ducote <ducotedt at stfran.com 
> <mailto:ducotedt at stfran.com>> wrote:
>
> Any ideas why extension mobility would stop working? The users are 
> able to log into the phone and it just resets with the original number 
> on the phone not the device profile number.
>
>  
>
> ------------------------------------------------------------------------
>
> This message contains confidential information and is intended only 
> for the individual named. If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail. Please notify 
> the sender immediately by e-mail if you have received this e-mail by 
> mistake and delete this e-mail from your system. E-mail transmission 
> cannot be guaranteed to be secure or error-free as information could 
> be intercepted, corrupted, lost, destroyed, arrive late or incomplete, 
> or contain viruses. The sender therefore does not accept liability for 
> any errors or omissions in the contents of this message, which arise 
> as a result of e-mail transmission.
>
>
> ***St. Francis Medical Center and affiliates encrypt email containing 
> Patient Health Information. You will receive a notice with 
> instructions on how to open any encrypted email you receive. To learn 
> more about this click *Here* 
> <http://userawareness.zixcorp.com/sites/index.php?b=141&type=1>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>  
>
>
> ------------------------------------------------------------------------
> This message contains confidential information and is intended only 
> for the individual named. If you are not the named addressee you 
> should not disseminate, distribute or copy this e-mail. Please notify 
> the sender immediately by e-mail if you have received this e-mail by 
> mistake and delete this e-mail from your system. E-mail transmission 
> cannot be guaranteed to be secure or error-free as information could 
> be intercepted, corrupted, lost, destroyed, arrive late or incomplete, 
> or contain viruses. The sender therefore does not accept liability for 
> any errors or omissions in the contents of this message, which arise 
> as a result of e-mail transmission.
>
> ***St. Francis Medical Center and affiliates encrypt email containing 
> Patient Health Information. You will receive a notice with 
> instructions on how to open any encrypted email you receive. To learn 
> more about this click *Here* 
> <http://userawareness.zixcorp.com/sites/index.php?b=141&type=1>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090506/a414cf1e/attachment.html>