Exchange UM transfering calls to CUCM

[Cameron Whitehead]

I am trying to setup CUCM to work with Exchange UM.  I have been able to successfully get CUCM to call into Exchange UM and take messages as well I can call an Auto Attendant I created.  The problem is that when Exchange UM tries to transfer a call back I get a prompt stating "The call cannot be transferred, returning to the main menu".

I have collected some logs during the call and I can see Exchange is sending a refer back into CUCM but it doesn't seem to be working still.  Here is the SIP refer message followed by a 202 Accept message that I get.

07/22/2014 13:49:54.148 CCM|//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from X.X.X.17 on port 5067 index 323 with 727 bytes:
REFER sip:callingnumber@X.X.X.30:5060;transport=tcp SIP/2.0
FROM: <sip:UMExtention@exchange.url>;epid=594A9989AF;tag=ceb39030bc
TO: <sip:callingnumber@X.X.X.30>;tag=9d01c512-f4dc-4f1e-81ef-dcc31ff35a08-52089133
CSEQ: 3 REFER
CALL-ID: 4dd84d80-3ce1c050-2b0-1e02010a@X.X.X.30
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP X.X.X.17:5067;branch=z9hG4bK13b4d580
CONTACT: <sip:exchange.url:5067;transport=Tcp;maddr=X.X.X.17;ms-opaque=ed5b6cc48304b78b>;automata;text;audio;video;image
CONTENT-LENGTH: 0
EXPIRES: 600
REFER-TO: <sip:TransferToExtention@X.X.X.30;user=phone;phone-context=dialstring>
REFERRED-BY: <sip:AAExtintion@X.X.X.30>
USER-AGENT: RTCC/5.0.0.0 MSExchangeUM/15.00.0913.000
P-ASSERTED-IDENTITY: <sip:AAExtention@X.X.X.30>

07/22/2014 13:49:54.153 CCM|//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to X.X.X.17 on port 5067 index 323
SIP/2.0 202 Accepted
Date: Tue, 22 Jul 2014 19:49:54 GMT
From: <sip:UMExtention@exchange.url>;tag=ceb39030bc;epid=594A9989AF
Content-Length: 0
To: "name" <sip:callingnumber@X.X.X.30>;tag=9d01c512-f4dc-4f1e-81ef-dcc31ff35a08-52089133
Contact: <sip:callingnumber@X.X.X.30:5060;transport=tcp>
Call-ID: 4dd84d80-3ce1c050-2b0-1e02010a@X.X.X.30
Via: SIP/2.0/TCP X.X.X.17:5067;branch=z9hG4bK13b4d580
CSeq: 3 REFER

This is using exchange 2013 and CUCM 7.1.5

[Cameron Whitehead]

Just wanted to add that after CUCM sends out the 202 Accepted message it then sends out 2 Notify messages.  One is a 100 trying and the second is a 404 Not Found message.

[Jonathan Schulenberg · Accepted solution]

Does the Rerouting Calling Search Space on the SIP trunk to/from Exchange UM have a CSS that can reach the TransferToExtention@X.X.X.30 referral destination? REFER messages are not subject to the standard CSS under Inbound Calls.

Also, you will likely want to set the Out-Of-Dialog Refer Calling Search Space and create a SIP Trunk Security Profile which accepts out-of-dialog refer, unsolicited notification, and replaces header. These are all related to the "Listen via phone" feature that users will see within Outlook.

[Cameron Whitehead]

Hi Jonathan,

It did turn out to be the Rerouting Calling Search Space on the SIP trunk.  I had set the Out-Of-Dialog Refer Calling Search Space as I thought that was the one used on a REFER message.  I did already have the other options setup as you suggested.

Thanks!