Extension Mobility - Host not found error

[yulem1968]

I have tried to set up EM - but when i try to log into phone (7911) i press the services button - host not found - is displayed on the display - just wondering if i have missed somoething out.

[david-lima]

Hi, check this good ducument for EM troubleshooting.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080093e72.shtml

Hope this help

David

[yulem1968]

Thanks for that David - found the solution in the document.

Replaced name of Call Manager with IP Address

Martin

[hitesh_patel]

Hello,

click on system -> Enterprise Parameters and wherever you see the name of your CUCM, replace it with it's IP address and save it. It will be fixed. The reason it shows, host not found is because currently your phone is trying to resolve the name of your CUCM through DNS which is not installed on your machine.

Regards,

Hitesh.

[yulem1968]

Thanks Hitesh

Other post pointed me to troubleshooting document where it said to replace name of call manager with IP Address - thanks for your response

Martin

[Alejandro Robles]

If the users weren't able to login using the extension mobility (CUCM 14) & on the collected (Via RTMT) TVS services logs you get these error messages:

17:14:18.405 | debug current session stuck in SSLhandshake 1467840992 pick next thread
17:14:18.405 | debug current session stuck in SSLhandshake 1468051360 pick next thread
17:14:18.405 | debug current session count is 1
17:14:18.405 | debug Unlocking of tvsPhoneThreadSessionMutex where session count less than max_sess and returning thread data 1468261728
17:14:18.405 | debug Returning thread data 1468261728
17:14:18.405 | debug ERROR:PostThreadMessage: write failed: -1
17:14:18.405 | debug ERROR:tvsPhoneMain:PostThreadMessage to tvs_thr->thrId: -268059840 failed. Clean up the resources. sessCnt: 2

17:14:18.405 | debug Maximum sockets available is = 1

Which was indicating we're hitting this bug :CSCvz51025
We (TACT)performed the workaround for the same that is restarting the TVS service which eventually resolved the issue.