Scenario#44 – CME Call Forward to Internal Extension not Working

I came across an interesting issue for a Swiss customer where they were having problem with Call-forward to an internal extension on their CME systems.

Call-forward to an internal extension seems quite straight-forward so I checked how telephony-service is configured and found both call-forward patterns as well as transfer-pattern were configured as .T .. so no real issue there. Customer added that it use to work fine before but not working anymore. After asking few questions I found that they recently migrated from ISDN to a SIP provider so all incoming calls are coming on SIP while I was thinking it’s all ISDN.

Ran our usual ccsip all, dial-peer all, ccapi inout debugs and found that when call is getting forwarded from 608 to 612, we are getting “SIP/2.0 302 Moved Temporarily” and then the call was getting disconnected.


SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP 62.2.x.x:5060;branch=z9hG4bKtjjtl830982hmqr9f6u0.1
From: 076XXXXXX<;user=phone>;tag=1680239575
To: 608<sip:0442296008@cableXXX:5060;user=phone>;tag=BA4F3C-6D2
Date: Mon, 24 Feb 2014 12:06:50 GMT
Call-ID: 7692dde2-11ccfac8-1ce04e37-1bb8@cableXXX
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Diversion: ;reason=no-answer;counter=1
Contact: <sip:612@192.168.x.x>
Content-Length: 0


When a call comes in on an SIP trunk and gets forwarded (CFNA / CFB / CFA), then the default behavior is for the CME to send the 302 “Moved Temporarily” SIP message to the Service Provider (SP) proxy. Sometimes provider may not support this and that was the case in this problem. Same issue is for Transfer as by default CME sends a SIP REFER message to Service Provider (SP) proxy and in this case SP was not able to handle it well.

I decided to configure the following commands before going to carrier as I was trying to disable this default behavior of CME.

voice service voip
no supplementary-service sip refer
no supplementary-service sip moved-temporarily

This fixed the issue without logging any ticket with carrier as I changed the behavior of CME.

Now when call is forwarded to 612 I was getting this instead of 302 Moved Temp.

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 62.2.X.X:5060;branch=z9hG4bKsn1fs200c8g1qq3af7f1.1
From: 072XXXXXX <sip:072XXXXXX@CableXXX:5060;user=phone>;tag=1247061884
To: 608 <;user=phone>;tag=12BA304-1D1B
Date: Mon, 24 Feb 2014 14:10:38 GMT
Call-ID: 5e59c683-7fa02bdf-214b80c1-5e8d@CableXXX
Allow-Events: telephone-event
Remote-Party-ID: “Michele 612” <sip:612@192.168.X.X>;party=called;screen=no;privacy=off
Contact: <sip:608@192.168.X.X:5060>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0


One thought on “Scenario#44 – CME Call Forward to Internal Extension not Working

  1. Hi
    I face a strange issue that when the CFNA set to my mobile it rings and when I answer the call it disconnects and also both FXO line stays OFF-HOOK for ever.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: