04-07-2013 01:21 PM - edited 03-16-2019 04:39 PM
We powered down our secondary call managers for maintenance the other day. The dashboard in cusp showed those elements down like it should.
When we turned them back on, 1 of our CUSP servers shows them online but the other doesn't.
My work around to get them back online it to delete the down elements, commit the config, add back the elements and commit the config. There's got to be a better way.
Any ideas?
06-24-2014 12:12 PM
I'm having this issue with CUSP and CVP. I turned off the CVP servers individually to test each one. When I brought them back online, CUSP thinks they are all still down.
06-24-2014 01:21 PM
I've upgraded our CUSP from 8.5.2 (original version when I first posted) to 8.5.5 and still have the same issue. Rebooting CUSP or deleting the element and re-adding it is the work around we've used.
If you have multiple networks ( we have a two one for inbound and one for the dialer ) each with its own listen point, try setting up a SIP Ping (under Server Groups) for each network, this seems to help.
Note* any time you reboot, you need to check to see if both SIP pings still show up,, it seems like the last one on the config is the only one loaded at startup.
09-10-2014 02:42 PM
make sure CUSP has only one IP interface and its address is used ping-options config for network, also check if SIP ping option is enabled globally by set "server-group sip global-ping"
09-10-2014 02:37 PM
make sure CUSP has only one IP interface and its address is used ping-options config for network, also check if SIP ping option is enabled globally by set "server-group sip global-ping"
09-10-2014 02:36 PM
make sure CUSP has only one IP interface and its address is used ping-options config for network, also check if SIP ping option is enabled globally by set "server-group sip global-ping"
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide