Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

calls not completing to 9971 from VCS side

I have an unusual issue here.

CUCM - 7.1.3

VCS - 6X

9971 - 9.0

C60 - TC4.1.0

Call from C60's registered with VCS as H323 endpoints can not call across a SIP trunk to 9971 video phones registered as SIP endpoints on CUCM. Working with TAC and have identified this as a reason for the call setup failure.

12/07/2011 23:43:15.232 CCM|//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from on port 25478 index 36892 with 901 bytes:

INVITE sip:6661@ SIP/2.0

Via: SIP/2.0/TCP;egress-zone=CUCMNeighbor;branch=z9hG4bK65139289f83b39ba650c074268d456fc41137.9ea38c26ce6e045c7fe529277702b25c;proxy-call-id=241dd556-2157-11e1-aa11-0010f31ed988;rport

Via: SIP/2.0/TCP;branch=z9hG4bK4f41519ef9157d4534e93b8683e06e4441136

Call-ID: 783a734a27f88f23@

CSeq: 52592 INVITE

Contact: <sip:4128591799@>

From: <sip:4128591799@>;tag=022bae8c5131cfc7

To: <sip:6661@>

Max-Forwards: 15

Record-Route: <sip:proxy-call-id=241dd556-2157-11e1-aa11-0010f31ed988@;transport=tcp;lr>


User-Agent: TANDBERG/4100 (X6.1)

Supported: com.tandberg.sdp.extensions.v1

Require: com.tandberg.sdp.bfcp.udp,com.tandberg.sdp.duo.enable

Session-Expires: 1800

X-TAATag: 241dd678-2157-11e1-a750-0010f31ed988

Content-Length: 0

12/07/2011 23:43:15.232 CCM|//SIP/Stack/Error/0xb4456168/Bad Extension - Require header processing failed.|<CLID::StandAloneCluster><NID::><CT::2,100,45,1.68627><IP::><DEV::><LVL::Error><MASK::40000>

So it's having an issue with:

Require: com.tandberg.sdp.bfcp.udp,com.tandberg.sdp.duo.enable

12/07/2011 23:43:15.233 CCM|//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to on port 25478 index 36892

SIP/2.0 420 Bad Extension

Date: Thu, 08 Dec 2011 04:43:15 GMT

From: <sip:4128591799@>;tag=022bae8c5131cfc7

Allow-Events: presence

Content-Length: 0

To: <sip:6661@>;tag=2070562717

Call-ID: 783a734a27f88f23@

Via: SIP/2.0/TCP;egress-zone=CUCMNeighbor;branch=z9hG4bK65139289f83b39ba650c074268d456fc41137.9ea38c26ce6e045c7fe529277702b25c;proxy-call-id=241dd556-2157-11e1-aa11-0010f31ed988;rport,SIP/2.0/TCP;branch=z9hG4bK4f41519ef9157d4534e93b8683e06e4441136

CSeq: 52592 INVITE

Unsupported: com.tandberg.sdp.bfcp.udp,com.tandberg.sdp.duo.enable

Has anyone seen this before?

If so, what specifically is needed to resolve?




calls not completing to 9971 from VCS side

On the VCS: Protocols --->SIP--->Configuration

Try turn off "Require duo video mode"

cheers jens

Please rate replies and mark question(s) as "answered" if applicable.
Cisco Employee

calls not completing to 9971 from VCS side

To have a better understanding of what's going wrong here can you please provide the following from VCS



netlog 2

place a call to reproduce the issue

netlog off

Also kindly asked to make sure that you follow the steps described in the VCS / CUCM deployment guide

Check the CUCM Trunk settings ( ie...  Media Termination Point Required settings ( disabled if you are placing video calls ) 

If still not working kindly asked the logs provided



Cisco Employee

calls not completing to 9971 from VCS side

HI Rob - You should see an ACK to this 420 and see VCS Re-Invite the call WITHOUT the required extensions in the empty Invite.  Do you see that in the CUCM trace?  Can you look passed this to see if you see that behavior? 

From what I've seen VCS should re-Invite the call without those extensions. Is there any other dialog happening after this occurs? Does the call fail or does it connect with no audio or video? I do believe the call ID tag will change when this occurs, but I may be mistaken.



New Member

calls not completing to 9971 from VCS side

First off, thank you for the suggestions above.

It was resolved by turning off one of the default SIP trunk settings in CUCM 7.1.3.

Whoever has ownership of this doc

may wish to add that you need to unselect
Use Trusted Relay Point*

CreatePlease to create content