Recent content by BobbR

A few years back I had a similar issue with a USB drive. Last resort was to squeeze down on the drive connector with thumb and finger, plugged it in again and it worked. Guess after untold plugging the connector pins spread enough to not make reliable contact. Worth a try.

WinXP does not require presence of a C: drive in order to boot up. My OS is installed on G:. C: drive is reserved for USB thumbdrive. Win Explorer shows first drive as D: unless the thumbdrive is plugged in, where it will then display the C: drive.

*03 is code for accessing a Legend CO port. 01 is the port number (1st Line port). This takes place within the PBX and gives you dial tone on Line 1. Then 72 is transfer code sent to Bell, followed by the number to transfer to. As mentioned above, *03 01 is intended for use in testing, not a...

Chris-- If I understand your statement, this does not sound correct: "OK, when I do this I can go to Switch Admin on the Audix and it brings up SPM. But, when I click pass-thru on the laptop it just sits here." When you dial in from your laptop you should hit the Legend, not the Audix. Since...

Yes, you can, with WinSPM and Passthru. Audix Administration, Start Log File (will have .log extension and readable as a .txt file). After starting the log file, do list ext, or list sub, list attendants. To determine which attendants are actually in use you would need to also do attendant...

This is an area that can really drive you bonkers, as it appears there is no logical reason for the system not to accept your renumber command to some digit range. But I'd wager that a printout of DIAL PLAN will show one or more Lines, Extensions, or Adjuncts has a 4, 4x, 4xx, or 4xxx number...

Legend R7 and Intuity Audix MAP5P R4. CEO called in, dialed extension, no answer, dialed *T for transfer to another extension, no answer, zeroed-out to Attendant, no answer. Could not escape from the loop to dial another extension. I can find nothing in documentation to allow another *T. He...

R6.0 supports the 008MLX modules. Probably a Board Renumber will be necessary for the system to properly recognize the new module.

What Franke said. I have had two connected via about 300 feet of CAT5E cable for several years. This cable might be overkill, but have had zero problems.

Legend R7, point-to-point PRI, Paradyne CSU each end to D100. Have developed a pronounced echo only on remote end, otherwise audio is crystal clear. More pronounced on CO calls but system-system intercom has them, on remote only. Outgoing over direct CO w/o routing to PRI are clear. All...

Thanks for the neat tip, will give it a try in a few days and test on my extension, since I'm one of the handful that wants this. I can envision a call bouncing around, routing over six T1 channels before hitting my VM (I'm on a slave system) so hopefully will not be two extensions doing this...

TTT, Your verbatim quote from the manual, on reading for third time, does say it will not work between systems, darn it. My initial interpretation had me wondering how the remote/slave system was commanding master system to route to voicemail since a NLUDP extension cannot be in Gp Cover 30...

What am I missing on setup of NL-UDP? The associated pattern for the extension range just routes to Pool 890 (Master Legend) with 3 digits. Calls are being routed correctly between systems. What additional coding is required to route DVM to Audix once the Master Legend receives a call? Since...

This seems my week for problems. Two Legends, R7, networked via PRI. Manual says I can send Direct Voice Mail to extension on other system. Code 56 procedure merely rings the extension rather than its Voice Mail. DVM works fine intra-system, but now have requirement for inter-system DVM...

Franke, I tried selecting Common Channel but to no avail, appeared to be selected but no change in printout. So, I set to T1 which wiped out info, then changed back to PRI and entered my parameters (actually, the correct settings were highlighted but I hit <enter> anyway. It magically went to...