05-22-2012 04:22 AM - edited 03-16-2019 11:16 AM
Hi,
My customers problem;
While in a call, he presses the conference button and as expected the other party is placed on hold.
He then searches his personal directory for the new participant, but the timeout seems to kick in and he gets an automated message to say that it is not possible.
He's using cucm7.0 and I can see a hardware conf bridge registered.
I can't replicate the fault on our own cucm 7.1
Sent from Cisco Technical Support iPad App
05-22-2012 06:17 AM
Hi there,
I can duplicate this behavior on our CUCM cluster (7.1(3b)su2). and it seems
that the IDT kicks in if you can't locate the user quickly enough It could be that
the customer has the T302 timers set @ a lower number than your cluster.
The IDT is seen in CUCM as the T302 timer
Try this info;
Configuring the Interdigit Timeout
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00800dab26.shtml
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen
05-22-2012 07:01 AM
Thanks Rob,
I presume adjusting the IDT will affect normal calls as well? Meaning if I set it for longer, then dialling will be delayed for normal calls.
I figured a work around....
1. Place first participant on hold
2. Search the directory and dial the second participant
3. Place him on hold as well
4. Hit the select soft key and select both calls
5. Hit the join soft key and hey presto!
Cheers
Dan
Sent from Cisco Technical Support iPad App
05-22-2012 07:11 AM
Hey Dan,,
Nice workaround my friend +5 for sharing this knowledge which
may help someone else down the road.
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide