I have a scenario here: 3725 router has fastethernet with ISL for two subnet address 184.108.40.206 for data vlan and 220.127.116.11 for voice vlan. and 18.104.22.168 was configured as srst source address in the router. Router is in remote office and running H322/SRST. On the phone we see srst is 22.214.171.124.
CCM version is 3.22. My question here is does the IP phone get SRST address from the router through the CCM or phone gets SRST address just based on its gateway address. I understand in CCM 3.3x you can specify SRST in CCM.
You need the "ip source-address" command in router, Bcuz the router should known which IP address it should use to communicate with the IP Phones in SRST mode. The phones will send request to register to the SRST router to the destination address 126.96.36.199, and the response should come from the same ip address. Without the "ip source-address" command, the phones will not register to the SRST router.
so this srst address is not used to register to ccm and then give to IP phones, only for kind of authentication. And also IP phone can get srst address regardless the router is ready or not as long as ccm has the gateway address of the router in the dhcp scope it'll give it to ip phone as srst address. I mean in 3.22. Am i right?I know well in 3.3x.
This SRST address on IP phone with 3.2 is the result of enabling SRST on the phone device config page (enabled by default). As the phone learns of its default gateway via dhcp, under its available Callmanager list it adds the default gateway/router as the next Callmanager after publisher and subscribers. It is not any authentication feature, but a fallback feature.
Yes, the ip phone can get srst address regardles of the router being configured for srst or not.
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.