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.
You said you already have G450s at your edge sites, but you didn't say whether you have an analog trunk card (MM711, etc.). If you do and the local Telcos servicing each edge site will sell you POTS you can connect to the MM711. Otherwise as @ZeroZeroOne says get an ATA and use ARS...
You didn't indicate what kind of trunking you have at your main location so I will tell you what my company does. We have SIP IPFLEX service from AT&T at our core data centers and most of our edge sites are without local trunking. We lease DIDs from AT&T and assign one to each location and...
Just spit balling here. I would think that as long as both domains are listed in Domains under routing would be all you'd need. Calls to/from/between SIP endpoints use SM database routing and not dial patterns.
Just a word of caution since all we have is a very narrow view into what you are doing and what equipment and applications you have. As soon as you mentioned entities, you imply you have SIP entities and possibly SIP endpoints. I would strongly encourage that you follow the "order of application...
You do not need to make any COR changes. Once the SA is enabled, the crss-alert button will have an additional field called 'Mntr Opt' to populate when you assign it to a button. The choices are Listen and none. If you assign listen, an additional press of the crss-alert button will service...
Yes. Enable SA8654 - Crisis Alert Call Monitoring and Recording on your CM. This will allow monitoring of the call. "Change system-parameters special" to get to the form.
Here is the description for SA8654:
Current Communication Manager has the capability of providing emergency alert signal and...
Looks like imt is not loaded on your CM or you need an Avaya login to access it.
mta msttrace.M
is all you're going to get. At least that should convert from hex to something readable.
Log in to AAMS GUI -> Tools -> Media Management -> Check box *Communication Manager -> Browse... -> Click on arrow to the left of Communication Manager -> Click ANNC.... -> Add Media -> Browse...
logc -t today MST > /tmp/msttrace.m
OR
logc -t today MST | logmst > /tmp/msttrace.M if trace analyzer is selected on 'ch mst' screen, then you can use
mta msttrace.M | imt > /tmp/trace
Hope you have a beany with a propeller ;)
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.