Cisco CUBE with Exchange 2010 UM

shell99102 · ‎12-22-2010

I'm working on a project to replace several Unity 4.0(5) servers with Exchange 2010 Unified Messaging. I'm working with the Cisco CUBE, which has H.323 connections to several different CallManager 4.1(3) clusters and a single SIP trunk to an Exchange 2010 UM server. I have successfully setup Inbound and Outbound dialing between the Cisco IP Phones and Exchange UM with G.729 Transcoding. I'm now trying to figure out how I can Translate and Relay the MWI SIP Unsolicited NOTIFY from Exchange UM through the CUBE to the CallManagers.

Has anyone used the CUBE for integration to Exchange 2010 UM?

Has anyone figured out how to get the MWI to work through the CUBE?

Any sample configurations?

Thanks,

Mike Shelley

Steven Holl · ‎01-06-2011

Mike ended up opening a TAC SR for this, but I figured I'd document the resolution in this post, since I just came across it, in case anyone else is trying this:

As we discussed, you want to get unsolicited MWI out of Exchange to be 
sent to a SCCP phone on a CM 4.x device.

CUBE does not support conversion of a SIP notify to an h323 message. 
You can see this in Table 2 of the CUBE configuration guide under 
'Supplementary Services> Message Waiting Indication' for h323-to-SIP 
CUBE.  It has support listed for 'No.'

The SIP trunk on CM 4 did not support NOTIFY messages, so you can't do 
SIP directly from exchange to CM (nor Exchange-[sip]-CUBE-[sip]-CUCM). 
If you look at the 'CUCM Trunks' section of the CM 4.x SRND, there is no 
mention of MWI support.

Note that with the CUCM 5 SRND, Table 5-2 under the 'CUCM Trunks' 
section lists MWI SIP support.  If you upgrade this CM to 5+, you should 
be able to integrate exchange with CM via SIP.

The only other way I can think of to maybe get something like this working would be if Exchange supported Q.SIG tunneling, which I'm not sure of.

matthewtravers · ‎04-18-2011

This is interesting, as we are facing a similar issue. Our situation however is SIP to SIP.

Our implementation is Ex2010 -> SIP Trunk -> Cisco SBC -> SIP Trunk -> CUCM 7.1.5

Inbound and Outbound calls are working as expected between Ex2010 and CUCM, however (I guess as expected), the unsolicited NOTIFY for MWI is getting blocked at inbound trunk on the SBC.

Is anyone aware of any possible configuration to allow the SBC to accept unsolicited notifications? The trunks on CUCM already have the necessary configuration applied, but that's not much good if it gets stop coming into the SBC.

Steven Holl · ‎04-18-2011

SIP to SIP CUBE Enterprise should support unsolicited Notify messages:

•    It receives unsolicited NOTIFY message requests without having to subscribe to the event that was
generated by the NOTIFY message request.

Make sure that you're running a recent version of CUBE (i.e. later 12.4T train or 15.x) and that 'mid-call signaling pass-thru' is configured. A SIP bind may mess things up if the messages come in a different interface. 'debug ccsip all' and 'debug voip ccapi inout' should shed more light.

navyvoicelab · ‎10-18-2012

We are having a similer issue with our system. We have "mid-call signaling pass-thru" configured as well as a new version of the CUBE IOS. The CUBE still will refuse to forward on an unsolicted notify message from our third party voice mail system to CUCM. Any other ideas?

matthewik.lee · ‎08-15-2016

Hi,

The CCM version is 8.0 and router IOS is 15.2(2)T2.

My setups are referred the url: http://voipnorm.blogspot.tw/2015/07/cube-to-exchange-2013-unified-messaging.html

UM is working but MWI feature.

The MWI cannot work and the cause should be "SIP/2.0 481 Call Leg/Transaction Does Not Exist" in the log below. 10.100.120.7 is the CUBE IP address. 10.100.200.21 is the Exchange 2013(mailbox role) IP address.

Aug 15 14:25:00.424: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
NOTIFY sip:6205@10.100.120.7:5060;user=phone SIP/2.0
FROM: <sip:6205@10.100.120.7:5060;user=phone>;epid=C14E55C0AC;tag=80cec79c3a
TO: <sip:6205@10.100.120.7:5060;user=phone>
CSEQ: 45 NOTIFY
CALL-ID: 2207ec29e5f14001afc3f2bbe600a6c4
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.100.200.21:54753;branch=z9hG4bK955fb5ea
CONTACT: <sip:6205@10.100.120.7:5060;user=phone>
CONTENT-LENGTH: 99
EVENT: message-summary
SUBSCRIPTION-STATE: terminated
USER-AGENT: RTCC/5.0.0.0 MSExchangeUM/15.00.0847.030
CONTENT-TYPE: application/simple-message-summary

Messages-Waiting: yes
Message-Account: sip:6205@10.100.120.7:5060;user=phone
Voice-Message: 1/2

Aug 15 14:25:00.424: //-1/xxxxxxxxxxxx/SIP/Event/sipSPIGetNotifyBody: Parse incoming NOTIFY message summary body
Aug 15 14:25:00.424: //-1/xxxxxxxxxxxx/SIP/Event/ccsip_call_notify_response: Queued event from SIP SPI : SIPSPI_EV_CC_NOTIFY_RESP
Aug 15 14:25:00.424: //-1/xxxxxxxxxxxx/SIP/Event/ccsip_api_initiate_subscription_termination: Queued event from SIP SPI : SIPSPI_EV_SUBSCRIPTION_TERMINATED
Aug 15 14:25:00.424: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 481 Call Leg/Transaction Does Not Exist
Via: SIP/2.0/TCP 10.100.200.21:54753;branch=z9hG4bK955fb5ea
From: <sip:6205@10.100.120.7:5060;user=phone>;epid=C14E55C0AC;tag=80cec79c3a
To: <sip:6205@10.100.120.7:5060;user=phone>;tag=1B851A54-17D0
Date: Mon, 15 Aug 2016 14:25:00 GMT
Call-ID: 2207ec29e5f14001afc3f2bbe600a6c4
CSeq: 45 NOTIFY
Content-Length: 0