I found this in the release notes:
Fixes for Customer-Reported Problems
The following customer reported problems fixes are resolved in Release 5.0 UR5
- no field found issues resolved in 5.0.2.14
-
Dpar Description of Problem
MN00604453 PRI trunks left in busy out state after yellow alarm is...
I don't know what software level you have but in release 5.0.1.11 the trap below was supposed to be fixed:
MN00320952 Main control reset, trap 13 @ 002C049C
I would upgrade to the latest I am aware of 5.0.2.14
I have a 3300 5.0 PR1 release 11.0.0.105_1 with embedded voicemail. I am familiar with MLAA to a point on the 3300 but was wondering if there is a workaround for the following. What essentially the customer wants is two instances of auto attendant. Currently they have an auto attendant with...
do you have the cos option 620 set to number of call logs allowed for each set. Call logging is available for 5330e and 5340e. You can access call logging from a 5340e sub attendant through the Superkey programmed as a feature key
you can change the condition of the room, clean, not clean, maid present etc but not the occupancy. Confirm with your pms vendor the status codes they have match yours.
if *2 is your maid in room code from form 2 then you would dial *2 plus the condition code you have set up with the pms vendor i.e. *2 plus 1 or *21 for maid is present in room
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.