Have you go this to work ? I`ve configured this before and my SI confirmed that the only way it worked was using CME,SRST. If you fail over to SRST and enter Show ephone registered , you do not see the VG`s or if you do then you do not see the DN`s concerned. I had to configure the VG224 as SCCP and then use CME, SRST feature with the MAC address and DN of the VG configured in the CME. The phones do not be added and will re-register to the router in the normal way with SRST. - Can you post the steps if you have cit configured and more importantly tested in SRST- thanks
abluenow – If I understand your question I believe we maybe doing what you’re after.We have a remote site running SRST.We have on site the following:
WAN Router – Cisco 3825 ISR (with just two interfaces, one to WAN the other to our Catalyst 3560 PoE 48-Port Switch)
SRST Router – Cisco 2821 ISR which supports analog (DID and FXO) interfaces and acts as the fallback when the WAN link fails (one interface just to the Catalyst 3560 PoE 48-Port Switch).Because of the analog interfaces, this voice gateway is setup for H323 (I’d personally rather have used MGCP but that protocol doesn’t support the analog interfaces).
sccp ccm 192.168.30.1 identifier 1 priority 1 version 3.1
sccp ccm 192.168.30.2 identifier 2 priority 2 version 3.1
sccp ccm 172.24.240.233 identifier 3 priority 3 version 3.1
sccp ip precedence 3
sccp ccm group 1
bind interface FastEthernet0/0
associate ccm 1 priority 1
associate ccm 2 priority 2
associate ccm 3 priority 3
switchback method graceful
The third CCM listed is the local SRST router (our 2821 ISR).This SRST router doesn’t have any “special” to support the VG224.Of course we loaded the 2821 ISR up with DSPs, it supports the local conference bridge, MTP (for call park, etc.) and transcoding.It also sources MoH for the location.
We tested this both in our lab and during deployment.Each time the Communications Manager servers were cutoff from the remote site (and during deployment we did that with ACLs on the 3825 WAN router) the VG224 (and all the IP phones) failed over (after about two minutes) to the on-site Cisco 2821 ISR.As long as the translation patterns were good (and that took a while to get just right), we were able to route “on-net” calls out the local analog interfaces without any issues.
My question is specific to when the VG224 fails to SRST, can the protocol between the SRST router and VG224 be H323.
The issue that I have is that my SRST router can not support all of the analog phones as sccp, there are a total of say 135 phones at the remote site and we only have a 2851 in this example. This is why I would like to run H323 in the SRST scenerio. I'm wondering if i can have two dial peers on the VG224 for each phone with different preferences, one as sccp and one as H323; this way SCCP to CUCM, H323 to SRST router.
If the above is not possible, with your current scenerio, do you know if you are able to assign different ports on the same VG224 to different device pools? I'm wondering about the possibility of configuring specific phones on each VG that will and will not register to the local SRST router (in the SCCP scenerio)
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.