cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
712
Views
0
Helpful
5
Replies

Not able to retrieve calls on hold

Erick Bergquist
Level 6
Level 6

Have issue where user puts call on hold, but is unable to retrieve them sometimes. It works fine most of the time.

CCM 3.3(3)sr3 and 5.03 phoneloads currently. Just dropped 5.06 on and will test with that.

Anyone seen this before? I did some forum searches and bug searches but so far haven't found a match.

5 Replies 5

Erick Bergquist
Level 6
Level 6

More information. The user isn't able to use the resume softkey or the hard key next to line to get call off hold.

Did the phone load upgrade fix this? We have someone experiencing something similar -

Mary Beth

We experience the same issue. Not too often though. I would like to know the answer to your question too.

Mike Aronhalt

Is anyone using H.323 gateways, and do those gateways have the 'Media Termination Point Required' checkbox checked in the CallManager Gateway configuration page? There is a bug CSCdy87397 which might come into play, but I'm not sure it's present in 3.3(3)sr3.

If you don't absolutely need an MTP in the middle of your conversation (and most deployments don't), it is safe and desirable to leave that checkbox off. However, if it's already off, it might be worth a try to turn it on, or turn it off if it's on. When an MTP is in the middle of an H.323 call, the way supplemental services such as hold, resume and transfer work are much different. Changing the setting could produce a change in the problem for better or worse, or no change at all, but the outcome would be of diagnostic interest in any case.

I have worked with Mr. Aronhalt in person on some other issues, so I have some knowledge of his AVVID topology. I note with interest that he and the original poster are running the exact same version and service release of CallManager, with similar if not identical phone loads. I reviewed the release notes for the newest 3.3(3) service release, which is 3.3(3)sr4a. I can't see any bugs fixed between there and 3.3(3)sr3 that apply here, so I don't know if it would help to apply it.

5.06 seems to have fixed up issues at the client I had that had this problem. Been 2-3 weeks and no reports of hold issue.