We were asked to conference three paging systems that way our public safety just has to provide the over head page twice. We are using an SV9500. Two of the systems are programmed as virtual stations call forward all to POTS line and the last one is setup as a trunk.
Basically we are looking...
We ended up resolving this with our distributor. Since the services weren’t stopped correctly before reboot the EOSN Service was not working correctly with the Telephony Event service.
The following resolved the problem
1) Stop E-OSN Server Service
2) Stop OW5000 TephonyEvent Service
3)...
Hello All
We have gotten a constant request to deploy soft phones in our SV9500 environment and while testing the MLC I think it would be a good solution except for the fact that I can’t figure out how to get the application to ring through the laptops speaker instead of their headset. It...
we recently needed to apply windows patches on our OW5000 server running on a windows server 2016 VM. After rebooting and applying patches, our UCE E-OSN clients are reporting server not connected even though they get the test notification when I send a test call through the OW5000 webui. Not...
It appears to be a tandem trunk issue. Checked ARRC and all trunks are allowed to connect to each other (Even the PRI D Channels). Not sure where to look next.
We currently ar experiencing a unique issue on our SV9500 platform with call transfers. When our UA5200 dterms built as an RSC of a 7 try to transfer a caller to an extension to that is call forward to cellphone outside the building, it calls the cellphone briefly then hangs up and recalls the...
This may be a longshot, but the models with a recording option have a setting for a “rec tone” which plays a beep to let both calling parties know that recording is in progress.
I believe it is Application Settings -> Recording Settings -> Rec Tone
We have heavily expanded our organizaing and our DIDs have grown expentionally. We currently use ACDD on our SV9500 to map the last 4 Digits of our Inbound DIDs to extensions. We are looking to did the last 7 digits now due to conflict. We were told we just have to change CDN 66 from 4 to 7 in...
Hello
We are currently decommissioning a UG50 at a remote site and are having trouble removing a route/trunks. The UG50 registers to a SV9500 switch. We have removed the route from AOPR and ARNP as well as removed the COTS care from the switch associated to the UG50 with AMGIL. We are still...
We use ALGSL for our third part SIP devices so they can sip register to the SV9500 and on our DT800/DT900’s we use it to assign the SIP recording license which we use ATSRL. When I say integration i may be using the wrong term but when some of these extensions call transaction boxes they’re...
We are having a weird predicament in my workplace were certain extensions built off of our SV9500(v8) can only access the opening box for f the voicemail (UM4730). This only occurs for some of our extensions that have ALGSL programmed for them. Removing AlGSL allows for the extension to...
Hello
I mostly operate day to day within the SV9500, rarely touching any of the SV9300 in our infrastructure. I recently was tasked with finding an appearance of another users extension on a second users phone. Has anyone found a way to similarly replicate the Sv9500’s LMLA4 command on a...
Hello All
We have a SV9300 with three of the 200 stations having their prime line key illuminated red when the station is in an idle state. You can still grab the line and take it off hook (basically it is not saying privacy release), and the light turns green when take it off hook. When you...
3racefan3 is correct. No physical buttons as well on these phones just a touch screen. I was told by a vendor that the only way to reset the Lock Screen pin was a certain command in SV9300/9500 in the original switch it was attached to, other than that it is a paper weight.
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.