Re: [OSL | CCIE_Voice] MWI Best Practice
Well, I don't know what will get you the points. The rumor I heard in regards to "best practice" is to use unsolicited. My experience is that unsolicited is reliable in a CME-CUE build. Just as reliable as the MWI On/Off. In a CME-SRST build, I have been using unsolicited without issue. Though, recently I have been testing with SIP notify since it will preserve the MWI status on failover. That said, I have (in my limited testing) seen that the SIP Notiy option is somewhat flaky. -- William Bell blog: http://ucguerrilla.com twitter: @ucguerrilla On Feb 19, 2013, at 11:05 PM, Pixar Perfect wrote: > Experts and wannabe experts friends, > > what are the best practices for MWI in CME and SRST modes for the CUE site > BR2? i was used to using MWI ON and MWI OFF DNs on a CME but i was told by a > fellow aspirant that MWI ON/OFF are not preferred (grading wise) and that > solicited MWI is that gets you to the needed points. > > however i have seen solicited and unsolicited to be verify unreliable on 7965 > phones .. you have to do no mwi sip and mwi sip to get solicited to work and > sometimes reboot CUE or router to get both solicited and unsolicited to work. > I am 1 month away from exam date and dont want to waste time exploring > instead adopt best common practice that works flawlessly ..and so far it has > been ON/OFF DN > ___ > 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
[OSL | CCIE_Voice] DHCP snooping test results
After playing with DHCP snooping for a while (i.e. pulling my hair out) , I have come up with an additional command that seems to be needed (on the router) if the scenario dictates that snooping needs to remain enabled on the switch. In my case I am using a 3560, not a 3750, and according to a lot of documentation i found the "ip dhcp snooping" command syntax and functionality varies a bit by switch platform. These results from my 3560 may or may not be identical to the 3750's behavior... If you have had issues of CUCM not assigning DHCP to Site A phones (or assigning to Site B but not Site A), you probably had DHCP snooping enabled on the Site A switch. After successfully breaking Site A DHCP via CUCM I setup the Site A router with local IOS DHCP, and this was broken by snooping as well. So, if CUCM DHCP doesn't work but IOS DHCP does, your issue is more likely to be with the CUCM server (possibly run "utils csa disable" if you've already verified the config and restarted the DHCP service.) If some sites get CUCM DHCP and others don't, or a site doesn't get any DHCP from CUCM or IOS, it's probably snooping. I would suggest using show commands to quickly see if snooping is enabled (sho run | i snoop), and if you're allowed to disable it that's the easy way - if not, practice reading through these debugs when snooping is interfering and again once you've worked around it. I found references in the solutions for OWLE labs 1 (p17) and 3 (p17) that state you can simply apply "ip dhcp snoop trust" on the switch ports facing the server (CUCM) and the router (a trunk). In the solutions for lab 3 there was also a test performed with an interface VLAN on the router, but when the DHCP request originates from the phone the behavior is slightly different – it seems that a switch with dhcp snooping enabled will set the "giaddr" to "0" in the option 82 header, and routers will typically ignore packets with the "giaddr" set to "0." Applying this command on the router tells it not to drop those packets with "giaddr" set to 0 as was done by my 3560 (I have not yet tested on a 3750 as I don't have immediate access to one): *Router# ip dhcp relay information trust-all* The following debugs helped identify these issues: *Switch3560# debug ip dhcp snooping packet* *Router# debug ip dhcp snooping packet * Attached is a text file showing relevant configs and commented debugs. I didn't want to put all that text in the email body because no one would want to read that email :-) Does anyone with a 3750 feel like testing this to see if it's relevant on that switch platform as well? Even if it's not required for a 3750 environment, I don't see how applying the command "ip dhcp relay information trust-all" on the router would break anything, and I'm going to add it to my routine script for Site A CLI. Hope this helps someone (besides me)... -Justin ! = 3560 switch, 12.2(46)SE Adv IP Services = ip dhcp snooping vlan 20 ip dhcp snooping<-- DHCP snooping enabled, need a few commands to work around if not permitted to turn it off vlan 10 name DATA ! vlan 20 name PHONES ! vlan 30 name SERVERS interface GigabitEthernet0/3 description Phone3 switchport access vlan 10 switchport mode access switchport voice vlan 20 spanning-tree portfast ! interface GigabitEthernet0/41 description HQ-SERVER-MacBook <-- CUCM running as a VM here on laptop switchport access vlan 30 switchport mode access switchport voice vlan 20 speed 100 duplex full no cdp enable spanning-tree portfast ip dhcp snooping trust <-- ADD LINE HERE to trust the DHCP server interface ! interface GigabitEthernet0/47 description HQ-RTR-Fa0-0 <-- trunk to router with L3 interface where ip helper-address is applied switchport access vlan 30 switchport trunk encapsulation dot1q switchport trunk native vlan 10 switchport trunk allowed vlan 10,20,30 switchport mode trunk switchport voice vlan 20 speed 100 duplex full no cdp enable spanning-tree portfast ip dhcp snooping trust <-- ADD LINE HERE to trust the DHCP server interface ! ! The following debug shows ip dhcp snooping processing packet, inbound to switch (phone on Gi0/3) and floods vlan 20 (router on Gi0/47) ! note there is nothing else coming back from the router or DHCP server Switch3560#debug ip dhcp snooping packet *Mar 1 01:44:39.141: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Gi0/3 for pak. Was not set *Mar 1 01:44:39.141: DHCPSNOOP(hlfm_set_if_input): Clearing if_input for pak. Was Gi0/3 *Mar 1 01:44:39.141: DHCPSNOOP(hlfm_set_if_input): Setting if_input to Gi0/3 for pak. Was not set *Mar 1 01:44:39.141: DHCP_SNOOPING: received new DHCP packet from input interface (GigabitEthernet0/3) *Mar 1 01:44:39.141: DHCP_SNOOPING: process new DHCP packet, message type: DHCPREQUEST, input interfa
Re: [OSL | CCIE_Voice] Questions regarding Unified CME as SRST
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 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
[OSL | CCIE_Voice] MWI Best Practice
Experts and wannabe experts friends, what are the best practices for MWI in CME and SRST modes for the CUE site BR2? i was used to using MWI ON and MWI OFF DNs on a CME but i was told by a fellow aspirant that MWI ON/OFF are not preferred (grading wise) and that solicited MWI is that gets you to the needed points. however i have seen solicited and unsolicited to be verify unreliable on 7965 phones .. you have to do no mwi sip and mwi sip to get solicited to work and sometimes reboot CUE or router to get both solicited and unsolicited to work. I am 1 month away from exam date and dont want to waste time exploring instead adopt best common practice that works flawlessly ..and so far it has been ON/OFF DN ___ 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
Re: [OSL | CCIE_Voice] Questions regarding Unified CME as SRST
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 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//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: ;tag=58ACCE8-1615 > To: > 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: > Accept: application/simple-message-summary > Content-Length: 0 > > Feb 18 21:13:11.067: //-1//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: ;tag=58ACCE8-1615 > From: ;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 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. >> >> >>
Re: [OSL | CCIE_Voice] Questions regarding Unified CME as SRST
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//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: ;tag=58ACCE8-1615 > To: > 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: > Accept: application/simple-message-summary > Content-Length: 0 > > Feb 18 21:13:11.067: //-1//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: ;tag=58ACCE8-1615 > From: ;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 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
Re: [OSL | CCIE_Voice] Questions regarding Unified CME as SRST
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
Re: [OSL | CCIE_Voice] Questions regarding Unified CME as SRST
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//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: ;tag=58ACCE8-1615 To: 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: Accept: application/simple-message-summary Content-Length: 0 Feb 18 21:13:11.067: //-1//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: ;tag=58ACCE8-1615 From: ;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 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
[OSL | CCIE_Voice] Questions regarding Unified CME as SRST
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
Re: [OSL | CCIE_Voice] SRST issues
1. I can confirm that I also don't see type added. I don't seem to be suffering the side effect of the VM button not working though. I assume it's not required for that functionality in SRST? 2. I don't have Fallback configured currently, but I believe it auto populates the E164 as the name. Not sure there's a way to customize that in traditional SRST? To preserve calls try: To preserve h323 calls you need to do the following to things: * * *From the gateway:* voice service voip h323 call preserve ! Call preserve allows the call to be sustained if all connectivity to UCM servers is down. SRST. * * *In CUCM:* Go to CUCM Advanced Service parameters. Set the *Allow Peer to Preserve H323 Calls* * * 3. I think MVA is only supported by scripts native to CUCM. If your connectivity to CUCM is down, you can't access the MVA service in CUCM. I'm pretty sure there isn't native support of MVA in the router itself. It just points to the service in CUCM. 4. These are options I use to manipulate ANI into CUC. There was a good discussion on this about a month back on this mailer. *Alternate Extension in CUC* * * On the Unity Connections server, under the users mailbox configuration, you can set an "alternate extension" This should be set to the ANI (Calling number) of the phone calling into voicemail when calling through the PSTN. You can check "debug isdn q931" on the SA router to determine what the inbound ANI is.* * * * *Calling Party Transformation Pattern on SA Device Pool* Preferred method when Alternate Extension is not allowed, because unlike the masking at the Hunt Pilot this preserves ANI for all other callers. Create a dedicated Partition and CSS for VM ANI manipulation. Then create a Calling Party Transformation pattern that strips the ANI of inbound calls to 4 digits and place it in the previously created Partition. I try to be as specific as possible here to meet the requirement for voicemail preservation. That way I'm not overlapping with other things. You can check "debug isdn q931" on the SA router to determine what the inbound ANI is. Apply the CSS to the the SA Device Pool at the Calling Party Transformation CSS field *Calling Party Transformation Mask on VM Hunt Pilot* * * Easiest to configure, but manipulates all inbound ANI to CUC. If you have a requirement to playback the calling party ANI it will only list 4 digits. Under the Hunt Pilot that you setup to reach your voicemail, you can set the Calling Party Transformation Mask to (This will then only send 4 digits to the Unity system for Calling number no matter where the call comes in from) On Mon, Feb 18, 2013 at 11:25 PM, Ramcharan Arya wrote: > Hello, > > I have couple of issues when site becomes SRST. > > 1. One ephone 1 and 2 it does not add phone type automatically. I'm using > one 7962 and one 7965 phone. > > ccm-manager mgcp-fallback > > telephony-service > srst mode auto all > > 2. My other site is H.323 gateway and I am using call-manager-fallback > > First of all my ie display showing E.164 number when making call to PSTN > > 2nd issue I am unable to preserve active call on H.323 gateway also keys > are not same when phone register to cucm > > This site has mobile voice access it does not work. Is there any solution > to change vxml script to use fall-manager-fallback feature. > > 4th issue : When I press message button I am able to reach mailbox using > alternate ext in Unity. Is there any other approach if I am not allow to > use alternate ext. > > > Please help me how should I fix these problems. > > Thanks & Regards, > Ramcharan Arya > CCIE # 28926 > > > ___ > 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
