UVM Issue between CUCM 8.6 and Exchange2013

[Suresh Subramanian]

Hi,

we have CUCM 8.6 integrated with Exchange 2013. if we call the UVM pilot (39990) let's say from IP phone-A(39903), it asks us to enter the extn number (IP phone-B, 37913) to leave the VM for.

If we enter the digits, Exchange sends Refer message to CUCM back.

>> When we entered the extn number of other mailbox (37913), we received the ‘REFER’ message from Exchange as below.

16:31:03.769 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 131.97.101.45 on port 5067 index 3463927 with 840 bytes:
[198611057,NET]
REFER sip:*39903@153.112.49.39:5060;transport=tcp SIP/2.0
FROM: <sip:*39990@131.97.101.45>;epid=6327C18D0F;tag=1970de9b9d
TO: <sip:*39903@153.112.49.39>;tag=65900990~e4066516-2467-4c7d-ae0c-e82ad64dd0c5-142063580
CSEQ: 1 REFER
CALL-ID: 6dad5e00-58916d95-1fce64b-27317099@153.112.49.39
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 131.97.101.45:5067;branch=z9hG4bKce45f05d
CONTACT: <sip:exchange.com:5067;transport=Tcp;maddr=131.97.101.45;ms-opaque=448fd090f5539347>;automata;text;audio;video;image
CONTENT-LENGTH: 0
EXPIRES: 600
REFER-TO: <sip:*39990@exchange.com:5062;transport=Tcp>
REFERRED-BY: <sip:exchange.com;c=ms-ova-data;v=1.0;Extension=*37913>
USER-AGENT: RTCC/5.0.0.0 MSExchangeUM/15.00.0995.032
P-ASSERTED-IDENTITY: <sip:*39990@131.97.101.45>

>> CUCM is accepting the REFER message received & sent 202 Accepted message back to Ex2013.

16:31:03.814 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 131.97.101.45 on port 5067 index 3463927 
[198611062,NET]
SIP/2.0 202 Accepted
Via: SIP/2.0/TCP 131.97.101.45:5067;branch=z9hG4bKce45f05d
From: <sip:*39990@131.97.101.45>;tag=1970de9b9d;epid=6327C18D0F
To: * <sip:*39903@153.112.49.39>;tag=65900990~e4066516-2467-4c7d-ae0c-e82ad64dd0c5-142063580
Date: Tue, 23 Jun 2015 14:31:03 GMT
Call-ID: 6dad5e00-58916d95-1fce64b-27317099@153.112.49.39
CSeq: 1 REFER
Contact: <sip:*39903@153.112.49.39:5060;transport=tcp>
Content-Length: 0

>> Now the New INVITE is generated based on the REFER-TO header & sent back to Ex2013 without the IP phone-B's extn 37913 in any header.

16:31:03.948 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 131.97.101.80 on port 5060 index 3463947 
[198611068,NET]
INVITE sip:*39990@131.97.101.80:5060 SIP/2.0
Via: SIP/2.0/TCP 153.112.49.39:5060;branch=z9hG4bK258b4c97822897e
From: * <sip:*39903@153.112.49.39>;tag=65901010~e4066516-2467-4c7d-ae0c-e82ad64dd0c5-142063646
To: <sip:*39990@131.97.101.80>
Date: Tue, 23 Jun 2015 14:31:03 GMT
Call-ID: 7867f300-58916da7-1fce653-27317099@153.112.49.39
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM8.6
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Cisco-Guid: 2020078336-0000065536-0002202182-0657551513
Session-Expires:  1800
P-Asserted-Identity: * <sip:*39903@153.112.49.39>
Remote-Party-ID: * <sip:*39903@153.112.49.39>;party=calling;screen=yes;privacy=off
Contact: <sip:*39903@153.112.49.39:5060;transport=tcp>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 218

is there anyway we can manipulate the Refer message so that in the next outgoing invite the extn 37193 will be present as Calling Number or some other header so that UVM will accept the message for that extn?

any help would be much appreciated.

Thanks

Suresh

[Suresh Subramanian]

Hi,

if someone faces the same issue with Exchange2013 & CUCM versions 8,9 &10, then here is the answer.

CUCM ignores REFERRED-BY, due a design limitation, we have an enhancement bug open for it which is CSCtf35144 (https://tools.cisco.com/bugsearch/bug/CSCtf35144/?reffering_site=dumpcr), since CUCM SIP trunk does not support RFC3515 completely, supporting incoming REFERs (both in-dialog and out of dialog) and we use only Refer-To and Replaces header in the incoming REFER message (to route the call), however not supporting Referred-By Header. This has been fixed on CUCM 11.0 version