Leslie/Steve/Jason, What are your thoughts on pre-configuring ephone-dns when you are permitted to use CME-SRST with autoprovision dn or all? Instead of dorking around with templates (which I hear is flaky) I was thinking about tweaking my approach to pre-configure ephone-dns when I build out SRST. I have done some basic tests and read the docs. It is supported and appears to work.
The benefits: I don't have to wait for phones to failover to finish SRST related configs. I can configure BACD, call coverage for VM, mwi sip, name, description, etc. Thoughts? -- William Bell blog: http://ucguerrilla.com twitter: @ucguerrilla On Feb 20, 2013, at 10:23 PM, Leslie Meade wrote: > Hey Steve, > > I just ran this via my lab and the light turns on.. > If I run debug ccsip messages I see the cue send a mwi notify to the ephone > and the light comes on > > > R3(config)# > *Feb 21 03:11:56.231: %IPPHONE-6-REG_ALARM: 10: Name=SEP001BD4607B13 Load= > SCCP41.8-4-1S Last=TCP-timeout > *Feb 21 03:11:56.279: %IPPHONE-6-REGISTER: ephone-2:SEP001BD4607B13 > IP:10.69.66.20 Socket:1 DeviceType:Phone has registered. > *Feb 21 03:11:58.615: %IPPHONE-6-REG_ALARM: 10: Name=SEP0017E066C2E7 Load= > SCCP41.8-4-1S Last=TCP-timeout > *Feb 21 03:11:58.679: %IPPHONE-6-REGISTER: ephone-1:SEP0017E066C2E7 > IP:10.69.66.21 Socket:2 DeviceType:Phone has registered. > *Feb 21 03:12:15.235: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: > Received: > NOTIFY sip:4002@10.69.66.254:5060;transport=udp SIP/2.0 > Via: SIP/2.0/UDP 10.69.66.253:5060;branch=z9hG4bKyHFdoT6xNYZ85fvOD9z4kQ~~1 > Max-Forwards: 70 > To: <sip:4002@10.69.66.254:5060> > From: <sip:4002@10.69.66.253:5060>;tag=ds3be1f82d > Call-ID: c234c79-1100@sip:4002@10.69.66.253:5060 > CSeq: 1 NOTIFY > Content-Length: 115 > Contact: <sip:4002@10.69.66.253:5060> > Content-Type: application/simple-message-summary > Event: message-summary > > Messages-Waiting: yes > Message-Account: sip:4002@10.69.66.253 > Voice-Message: 1/0 (0/0) > Fax-Message: 0/0 (0/0) > > *Feb 21 03:12:15.243: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: > Sent: > SIP/2.0 200 OK > Via: SIP/2.0/UDP 10.69.66.253:5060;branch=z9hG4bKyHFdoT6xNYZ85fvOD9z4kQ~~1 > From: <sip:4002@10.69.66.253:5060>;tag=ds3be1f82d > To: <sip:4002@10.69.66.254:5060>;tag=3BF3A8-1459 > Date: Thu, 21 Feb 2013 03:12:15 GMt > Call-ID: c234c79-1100@sip:4002@10.69.66.253:5060 > CSeq: 1 NOTIFY > Content-Length: 0 > > > > sip-ua > mwi-server ipv4:10.69.66.253 expires 3600 port 5060 transport udp unsolicited > ! > ! > ! > gatekeeper > shutdown > ! > ! > telephony-service > srst mode auto-provision all > srst ephone template 1 > srst dn template 1 > srst dn line-mode octo > max-ephones 30 > max-dn 30 no-reg both > ip source-address 10.69.66.254 port 2000 > time-zone 42 > voicemail 4220 > mwi relay > max-conferences 8 gain -6 > transfer-system full-consult > transfer-pattern .T > secondary-dialtone 9 > create cnf-files version-stamp Jan 01 2002 00:00:00 > > From: ccie_voice-boun...@onlinestudylist.com > [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Steve Keller > Sent: Wednesday, February 20, 2013 12:23 PM > To: Jason Lee > Cc: ccie_voice > Subject: Re: [OSL | CCIE_Voice] Questions regarding Unified CME as SRST > > Well i confirmed today that if using a CUCM->CUE integration at a branch > site, th you will want to setup your MWI to be subscribe/notify when you > complete your CUE integratoin with CUCM. MWI works great when registered to > CUCM and using CUE for VM. When the site fails over in to srst mode and your > phone has an existing MWI on it, this is what you would want to do in order > to preserve that MWI lamp. > > 1) When integrating your CUE to CUCM choose MWI type subscribe/notify. > 2) When building your router config for SRST, make sure to build an > ephone-dn-template that specifies MWI SIP that will get applied to the phones > when they register (under your telephony service). > > 3) when configuring sip-ua / mwi-server i did not use unsolicited key word > > this has allowed the current MWI lamp to stay lit when failover to unified > CME as SRST. When integrating using "unsolicited" notificiatoins I was not > maintaining the MWI lamp on during failover. > > i am using 7975 model phones and i bounced the failover a few times and it > seemed to work pretty consistently. please try at home and let us know if you > have the same results with this if you are interested. > > > > > > On Tue, Feb 19, 2013 at 11:33 PM, Jason Lee <jas7...@gmail.com> wrote: > I typically use unsolicited on my SRST sites for MWI, but you may be on to > something. Maybe this method would be preferred. All depends what they are > looking for! Thus begins my tangent ;o) > > I've seen the same behavior with the + as Bill. > > > > Sent from my iPhone > > On Feb 19, 2013, at 9:55 PM, William Bell <b...@ucguerrilla.com> wrote: > > Steve, > > Jason's response is spot on for your first question. Though, I have found the > integration to be a little flaky myself. But that was a recent observation > when I was trying pre-build ephone-dns before swinging a site to CME. > > In regards to your second question, I don't think the phone is display the > "+" on the call plane. But it should display it in the status line at the > bottom of the screen. > > -Bill > > -- > William Bell > blog: http://ucguerrilla.com > twitter: @ucguerrilla > > > > On Feb 19, 2013, at 4:33 PM, Steve Keller 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
_______________________________________________ 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
