cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
919
Views
0
Helpful
4
Replies

Directory on midlet not showing listings

alanfranks
Level 1
Level 1

Having recently upgraded from Call Manager ver 7.1.3 to 8.6.2.200 on Cisco's recomendations we are now encountering an issue with the phone milet and its ability to see the directory listing. this was working ok prior to the upgrade.

Prior to the upgrade we had 22 endpoints on SIPTS.1-6-4-4072r-k9.sbn and all phones on sip75.8-5-3s and using midlet TSPM.1-6-1-0s, this would display all the one button to push information on the midlet including the directorys

Since upgrading to version 8.6.2-20000 we have lost the directory information on the midlet - error no results found - unable to connect to directory. please try again.

We have upgraded 5 endpoints to CTS 1-7-6-4-k9.sbn and 5 phones to sip75.9-2-1s and now using midlet TSPM-1.7.4-P1-2S to see if this would resolve the issue but we are still experiencing the same problem.

We can use the directory hard button and go to the corporate directory and search and see the listings but when selected it will only make a voice call and not video....

any assistance on this would be great

Thanks

Alan

4 Replies 4

antigles
Cisco Employee
Cisco Employee

Hi Alan,

You are hitting bug CSCtu07566. Upgrading CODEC and midlets to 1.8.1 or 1.8.2 should make it work.

Using the directory hard button on the phone and launching the call from there makes the call to be started from the IP phone and not from the codec. That is the reason for the audio only that you see but that is normal.

Best regards.

Thanks Antigles

We need to do a staged upgrade of all 22 codec to 1.7.6 first then procede to 1.8.0 and above as 1.8.0 and above is not compatable with our 1.6.4.firmware according to the compatability matrix.

Regards

Alan

Hi  Alan,

Correct. Compatibility matrix is always to be taken into account. Having CTS 1.6.4 talking to CTS 1.8.2 might or might not work becasue it is marked with a "P" meaning "presumed to work but not tested". You should also have into account the version of all your other components, like CTMS, CTS Manager and so on.

On any case, I would recommend testing first with only one room to make 100% sure if the upgrade will fix your directory issues before thinkig about upgrading the rest. Once you confirm 1.8.2 upgrade fixes it you can decide on the upgrade strategy.

Best regards.

Hi Antigles

The CTMS and CTS-Man have all been upgraded and running v1.8 also - last thing to do was the CUCM and endpoints/phones/midlets. one thing that did have me puzzled was the difference between the http interaction from a sip75.8-5-3s compaired to the sip75.9-2-1s...

All phones that have not had the upgrade are all pointing to http addresses for the following

Information URL  http://xxxxxx:8080/ccmcip/GetTelecasterHelpText.jsp

Directories URL  http://xxxxx:8080/ccmcip/xmldirectory.jsp

Services URL  http://xxxxx:8080/ccmcip/getservicesmenu.jsp

Authentication URL  http://xxxxx:8080/authenticate.html

and the upgraded phones all seem to want to to use https and take the defaults from the enterprise parameters

Information URL  https://xxxxx:8443/ccmcip/GetTelecasterHelpText.jsp
Directories URL  https://xxxxx:8443/ccmcip/xmldirectory.jsp
Services URL   https://xxxxx:8443/ccmcip/getservicesmenu.jsp
Authentication URL  https://xxxxx:8443/ccmcip/authenticate.jsp

Its not causing an issue that we are aware of (YET) but would rather understand why its trying to get a secure connection to all the services etc when the CUCM is in non secure mode.

Regards

Alan