I have been setting up my CUE to use outcalling/unsolicited for MWI when doing the integration with UCM. Using the sip-server/unsolicited command gets my mwi working for subsequent voicemails, but the phone is definately not subscribing, so it can get updated MWI as it becomes registered locally. It kind of sounds like this is the flaw in my approach. Now that i think of it, outcalling would probably only be valid in a CME integration with ephone-dns for MWI. Now that i am either registered to UCM for MWI or to SRST, it does make sense that i should be sending subscribe messages via sip to get MWI status from CUE.
On Tue, Feb 19, 2013 at 9:29 PM, William Bell <b...@ucguerrilla.com> wrote: > Jason, > > I have recently been toying with the idea of pre-building my ephone-dns > for scenarios where a site is a CME-SRST site and I am allowed to use > autoprovision dn or all. I like to build out my entire config in notepad > before pasting it in and I like to fine tune the ephone-dns before they are > in SRST mode. > > I have a done a couple of tests using this method and it seems to work > fine. Though, I did see some flaky behavior with Subscribe Notify and MWI. > Which is the cornerstone of my tangent ;-) > > -Bill > > > -- > William Bell > blog: http://ucguerrilla.com > twitter: @ucguerrilla > > > > On Feb 19, 2013, at 8:04 PM, Jason Lee wrote: > > Steve, > > I think that if you set up Subscribe Notify for MWI instead of Unsolicited > Notify it might preserve the light. In order to get that to work you would > have had to load the phones into SRST (auto provision all) at least once so > that they populate the running config. You can then configure the "mwi > sip" option under the ephone-dn. That will force it to subsribe to to the > CUE for MWI updates. I imagine that subscription happens every time the > phone comes online or in this case when they register to the CME-SRST > router during failover. It should then be followed by a notify with the > MWI status. > > I did this on a straight CME lab yesterday and pulled the following > traces. Given that occurs every time the phone boots up, you should meet > your requirement. I'll test tomorrow since I'll be doing a 3 CUCM site lab. > > r2800-2j-b(config-ephone-dn)#mwi sip > r2800-2j-b(config-ephone-dn)# > Feb 18 21:11:30.316: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: > Sent: > SUBSCRIBE sip:3002@192.168.106.2:5060 SIP/2.0 <------ HERE > IS THE SUBSCRIBE MESSAGE > Via: SIP/2.0/UDP 192.168.106.1:5060;branch=z9hG4bK191EA4 > From: <sip:3002@192.168.106.1>;tag=58ACCE8-1615 > To: <sip:3002@192.168.106.2> > Call-ID: 996B6A71-794611E2-80CEE1A3-4F484EB8@192.168.106.1 > CSeq: 101 SUBSCRIBE > Max-Forwards: 70 > Date: Mon, 18 Feb 2013 21:11:30 GMT > User-Agent: Cisco-SIPGateway/IOS-12.x > Event: message-summary > Expires: 3600 > Contact: <sip:3002@192.168.106.1:5060> > Accept: application/simple-message-summary > Content-Length: 0 > > Feb 18 21:13:11.067: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: > Received: > NOTIFY sip:3002@192.168.106.1:5060 SIP/2.0 > Via: SIP/2.0/UDP 192.168.106.2:5060;branch=z9hG4bKUNWTUT.iNZVt5tr6uAHS+A~~3 > > Max-Forwards: 70 > To: <sip:3002@192.168.106.1>;tag=58ACCE8-1615 > From: <sip:3002@192.168.106.2>;tag=dec1fdb9-1100 > Call-ID: 996B6A71-794611E2-80CEE1A3-4F484EB8@192.168.106.1 > CSeq: 3 NOTIFY > Content-Length: 114 > Contact: sip:3002@192.168.106.2 > Event: message-summary > Allow-Events: refer > Allow-Events: telephone-event > Allow-Events: message-summary > Subscription-State: active > Content-Type: application/simple-message-summary > > Messages-Waiting: yes <--------- > HERE'S THE NOTIFICATION OF MWI ON > Message-Account: sip:3002@192.168.106.2 > Voice-Message: 1/0 (0/0) > Fax-Message: 0/0 (0/0) > > > On Tue, Feb 19, 2013 at 4:33 PM, Steve Keller <skeller...@gmail.com>wrote: > >> Recently i have noticed a few things in my lab as i have been preparing >> for the lab exam. >> >> Using CME as SRST specifically in this situation, i have been trying to >> "preserve" as much features and appearance as i can when my UCM phones >> register to the gateway. >> Two scenarios i have question on because i cannot seem to get them to >> work. >> >> 1) If my branch 2 phone has a voicemail and MWI turned on, when it falls >> back to Unified CME as SRST the MWI does goes off, however i can retreive >> the vm because my CUE integratoin does remain in tact. Is it possible to >> have the phones fail over and maintain the MWI status automatically? If i >> leave a new vm while in SRST mode then the light does come on. >> >> 2)When making a call from the UCM phones to my BR2 phones (CFUR) the call >> comes in and at the gateway level i see the ANI is full e164 format >> including the + character. However the phone never shows the plus character >> in SRST mode. Is this possible? Does Unified CME as SRST support the + >> character? >> >> I am thinking if this is possible it would be nice to include these >> capabilities as part of my config if asked to preserve features, >> functionality while in SRST. >> >> thanks in advance all..... >> >> >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> >> Are you a CCNP or CCIE and looking for a job? Check out >> www.PlatinumPlacement.com >> > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com > > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
