The EM200 is hot pluggable. You can power down the G430 if that makes you feel better but if you do not want to interrupt service on the G430 itself, just unplug it from the G430 and power.
It's been a minute but to park a call isn't the sequence something like this:
1. establish the call
2. hit transfer button and receive dial tone
3. hit park button
4. hang up
Does anyone have a config note that shows the settings/certs needed to register a B199 to Session Manager using TLS (please don't send me a link to the B199 Admin PDF)? We have other endpoints registered to same ASM using TLS on same port (5061), so I feel like it's the B199 configuration, but...
Since there is no automatic failover for SM, you do not have to disable geo before restarting either SM or SM-Geo. Be mindful that any application getting its license from SM will go into license error mode while SM is down. It usually takes ~15-20 min to fully restart.
Make the group smaller or consider overhead paging. If phones in the group are close to each other, consider removing some from the group as they can "hear" the page from the adjoining phone. When you group page, CM has to allocate resources for each phone before you will receive DT to proceed.
set mgc list CoreCM_IP,ESS_IP,LSP_IP
set reset trans 1
set reset tot 10 (a good starting value, see next comment)
set reset pri 2 (this setting and the previous one should be designed with the LLDT and other timers in CM in mind)
CM 10.2 has to be able to successfully connect to a standalone or embedded WebLM (SM) even if you don't have a valid license loaded. After that happens, you will have 30d to make adds/changes after which you will need a valid license loaded to continue to administer.
Hi, not sure what @kyle555 was referring to as I don't see SA8096 in the 2023 version of the CM special applications PDF. However, a lot of the SAs have been mainstreamed in the later CM releases. But regardless, be sure and check with your trunk vendor as most of them default to throwing away...
Your screenshot shows that it is mapped to 127.0.0.1:3389. Put that into RDP client (3389 can be omitted as its RDP's default port).
You should be using the Enhanced SAL V2. It actually maps the customer's IP to your PC through SAL.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.