08-10-2017 08:36 AM - edited 03-18-2019 01:23 PM
Hi, dear support community.
Can someone help to clarify this, please:
TMS 15.5 plans a conference based on Conductor XC4.3.1, which is connected to CUCM 11.x via SIP trunk.
Conference starts fine; however, if add a cell phone to dial out, Conductor sends SIP whiteout Source field. It is only an IP there.
Conductor doesn't pass a conference number.
08-10-2017 01:27 PM
Is this only seen on one particular device or several, and which ones?
What conference bridge is being used with Conductor?
Is the display name blank, the source address, or both?
08-11-2017 12:06 AM
Hi, guys. Thank you for answers.
It is seen both at CUCM site and at Conductor call logs since in INVITE the From field shows a name of a conference instead of Calling Number. This name is successfully shown at a jabber window if add it to a conference. However, CUCM receives no Calling Number, passes it to GW and GW drops the call.
(Yes, it is easily to correct by configuring translation rule, but I wish Conductor sends appropriate INVITE). TPS 4.4 is used as a conference bridge with Conductor.
08-10-2017 08:40 PM
Unfortunately, this is expected behavior. When Conductor dials out, it doesn't use a valid source SIP URI or meeting ID, unlike MCU or stand alone TP Server. Because of this, Conductor works much better with dial in and/or One Button to Push, as opposed to Automatic Connect.
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