Audio: No Audio After Consult Transfer

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(New page: == No Audio After Consult Transfer == <table border="1"><tr><td> '''Problem Summary''' </td><td>There is no audio between the caller and Agent 2 after a basic video call transfer is compl...)
m (Bot: Adding {{Template:Required Metadata}})
 
(One intermediate revision not shown)
Line 1: Line 1:
 +
{{Template:Required Metadata}}
== No Audio After Consult Transfer ==
== No Audio After Consult Transfer ==

Latest revision as of 18:47, 18 December 2009

No Audio After Consult Transfer

Problem Summary There is no audio between the caller and Agent 2 after a basic video call transfer is complete.
Error Message No message.
Possible Cause When using CUPS 7.0(1), a re-INVITE glare condition might occur, which causes a SIP deadlock situation where CUCM does not resend a re-INVITE after the 491 Request Pending instance.

Specifically, the caller and agent initiate an INVITE simultaneously and then each waits for an ACK. After a timeout delay, both parties reinitiate an INVITE. The glare condition results in the agent reinitiating the INVITE; however, the caller does not. Instead the caller ignores the new INVITE and continues to wait for an ACK from the agent.

Recommended Action There are two possible solutions for the cause of this problem:
  1. Choose a

solution:On the CUPS server, use TCP as the “Protocol Type” for the CUPS static routes. On the CUCM server, use TCP as the “Outgoing Transport Type” for the SIP Trunk Security Profile that is used for the VRU leg of the transfer.

  1. Enable Media Termination Point (MTP) on the SIP trunk and point it directly to CVP, instead of CUPS. This is the trunk for the VRU label route pattern. This solution allows for the use of UDP.
Release Release 7.0(2)
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools