Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Internal telephony error 58

Unanswered Question
Jan 6th, 2012
User Badges:


Some of our user are using Genesys desktop to receive calls from free numbers.  They have cisco softphone but most of the time the Genesys application are unable to login and gives an error "Internal telephone error [58]. The problem is resolved temporarily when we re-add the user's number in controlled device in CUCM under pgenesys and ask the user to restart the genesys application but we need a permanent solution for this. We checked with Genesys too but they said the problem is from voip end. Can anyone advice what could fix the issue.

Version - CUCM 7.1.3.



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Paul Heilmeier Mon, 10/28/2013 - 06:30
User Badges:

Hi Amit,

looooooooong time ago your post.

Can only acknowled your issue, with CUCM 8.6.2a(SU2)

We are using EM & CIPC, and sometime (but really really rare) the user get the message "out of service 58".

If the same EM use a other device it works. only solution, delete Device add Device again (same CIPC name) and it works.

I can't figure out what happens, seems an  CUCM DB-CTI-Device Issue.



mark_fox Mon, 12/16/2013 - 07:28
User Badges:

Hi Amit,

Was there ever a resolution to this issue?  I'm currently having a similar issue running CUCM 8.6.2.

Thank you,


Paul Heilmeier Mon, 12/16/2013 - 07:34
User Badges:

Unfortunately not...

i opend an SR, the result of the BU was "it isn't an Cisco fault, maybe the CTI Application stores a wronge IP Adress in the cache and doesn't release them, also not after an update".

An restart of the CTI Service on the CUCM could help, but we won't to try it, cause it is an productiv system, and our workaround was to delete and reinsert the affected device.



mark_fox Mon, 12/16/2013 - 07:55
User Badges:

Did you also engage a Genesys resource?  I've restarted the CTI Manager service and I'm still seeing the same results.  My current fix is to un-associate and re-associate the CIPC from the application user.  Not a great fix.



This Discussion