Search results for query: *

The PBX requirements from the DSE config note for state: 3.0 PBX HARDWARE REQUIREMENTS • G3, IP600 & S8500/S8700: Digital port (TN2224) to support 7434D/8434D, one per MAS port. I would not deviate outside of the recommended hardware as you may be denied technical support or void your...

Do you have any UDP stations on the remote site? Can you provide just the voicemail extension entries from your UDP and AAR table on the remote site? Regards, Seezer

Sounds like your two sites are connected via DCS tie trunk. The voicemail extension at your remote site needs to be programmed for UDP and AAR. The voicemail extension at your main site so no need for UDP there. Regards, Seezer

Mitch, Your advice was correct! I left the CM side untouched and only configured the BCMR server settings to point to the S8300, used 5023, and it connected. I never would've figured this out. Thank you.... Regards, seezer

S8300/G700/CM R4.0.3 I'm unable to program the ip-services for BCMR connectivity on an S8300. When I set the service type as 'SAT' and set the local node as 'procr', the system returns "procr" Local node name cannot be procr if service type is SAT'. I have processor ethernet enabled in my...

We've had the same issue with a G700 and HP 5400. It is a known issue and HP is supposed to be releasing a special GBIC to resolve. You can read about it in the following document, page 69. http://cdn.procurve.com/training/Manuals/yl-zl-RelNotes-K1251-59914720.pdf Regards, Seezer

Consider applying service pack 4. Taken from the SP4 release notes: Summary of MAS issues fixed in this service pack wi00016319 At times, Call Me and Notify Me stop working. http://support.avaya.com/elmodocs2/mm_r3_1/MM310400_Release_Notes.html Regards, Seezer

Thanks pabxdude. Sounds like the private domain is the way to go unless otherwise requested by the customer. I certainly do not want to rebuild the servers after they are cutover. Regards, Seezer

Hello Ken, When you trace the call using OHV, the calling extension information is blank? Is this true for both internal and external calls? Regards, Seezer

Thanks for clarifying that Ken. Regards, Seezer

Greetings, I've done several installs in the past in which MM resided in its own private domain. Now, I'm paying more attention to these choices and trying to determine difference between joining a private Windows domain vs corporate Windows domain. The concept and planning guide indicates...

Thanks Ken. I am hesitant to install an application on the MAS without knowing if there will be an adverse affect. Regards, Seezer

Greetings, Is anyone using an Internet-based remote access application such as GoToMyPc or Logmein to access their MAS? If so, any feedback to share? Regards, Seezer

Unfortunately, I don't know if 96xx phones aliased as 46xx phones can take advantage of the survivable gatekeeper field. Maybe someone can chime in. Regards, seezer

If your statically programmed phones are 46xx models, you can specify the LSP node name in the survivable gatekeeper field. It is on the first page of the station form. Regards, seezer

Without knowing the details about your MM, I recommend a 'list trace station xxxx' from any phone as you call the hunt group extension. Other troubleshooting steps (from the PBX side) are status your trunk and signaling group if using T1 or H.323. Status your voice mail ports if using DSE...

Thanks sirius. I'll install the service pack and then the latest patches. Regards, seezer

Greetings, I am preparing to apply MM R3.0 (MSS) service pack 3 for a customer. The MM is running the GA release and does not have any service packs or patches. I've read the readme file and it appears that SP3 is cumulative, and contains SP2, SP1, and subsequent patches. Can I skip SP1/SP2...

Thanks Ken. I checked the timer settings on our system (no luck), but will also check our customer's system. Regards, Seezer

Our customer w/MM R3.0 (T1 QSIG) reported that their attendant was having problems picking calls that resulted from a '0' out operation (either from the mailbox or Caller App). We recreated the issue on our system (R2.0 w/H.323) and observed that it takes MM three seconds to release the call...