EliteMail LX - Random transfers - PBX Info :: Your Free PBX, PABX and Telephone Information Resource

ILE · 04-17-2007, 07:06 AM

Elitemail LX installed in IPK with PRT incoming and DNIS (all incoming calls use same dnis). Using 1-1-22, day mode is directed to extension 300 (VM), at night however, calls are directed to tenant 00. Day mode is fine. The situation is that incoming calls need to ring at a few phones in night mode before being answered by voicemail. Sounds simple, but voicemail answers with "enter your security code", or goes directly to a random personal greeting, or transfers to a random extension. Currently, the voicemail has CO line appearances and delayed ringing for those lines. You cannot use DIT for inbound calls from a PRI because digit conversion is enabled. Besides, I tried. I have tried ring immediate on vm station ports with delay answer on the vm ports. I have tried using a CAR key. If I set 1-1-22 to telephone instead of tenant, no problem. I have checked 1-1-77 and 1-2-22 and 1-2-26 for conflict. Yay.

***Doghart*** · 04-17-2007, 08:06 PM

I am confused. You say you have a PRI and are using 1-1-22, but then say the voicemail ports have co appearances and use delay ringing?

The typical way I do this is to send the DNIS in 1-1-22 to an SIE key that appears and rings on the digital phones for night mode and fwd that car to vm pilot 300 on a no/ans. As long as there is no mailbox for that CAR/SIE your main greeting will play.

D

ILE · 04-18-2007, 04:57 PM

I guess I failed to say....that's how it was, and my previous post is what I did to troubleshoot. The voice mail was recently replaced - Elitemail CTI to Elitemail LX. Things were fine before, although I was not the one to replace it. Some other jack-leg had been in it and there was much I had to redo.
The problem with sie on this is that at night the did assignment is tenant-wide, so incoming calls are treated as normal ringing. I could be wrong though...

ILE · 04-18-2007, 05:02 PM

Wait, strike that. I just absorbed what you said. At night, instead of tenant wide, direct the call to a sie that rings immediate on the stations that need to ring, and 45-300 the sie to vm? Does the vm pilot need an appearance of the sie, and does it ring?

ILE · 04-18-2007, 05:06 PM

Once again...still sinking in. Your post is completely clear. VM ports have cap keys and that's all they really need. Thank you for the help. Just for reference though, could the vm pilot have the sie on delay ring 4-37?

***Doghart*** · 04-18-2007, 09:42 PM

I would config like so:

DAY:
1-2-22 DNIS digits route to SIE 250 day mode
SIE 250 appears on mulitple phones in 4-12
SIE rings on those phone in day mode in 4-37
Option: CFD 250 no/ans to vm pilot 300, insure no vm box 250 exists

NIGHT:
1-2-22 SAME DNIS digits route to SIE 251 night mode
SIE 251 is cfd all calls to vm pilot
Insure there is no mailbox 251

I typically delete all button programming from the digital VM ports. They do not need line appearances or CAP keys.
If you do not have any analog trunks, I would suggest deleting any ringing programmed in 4-01 and 4-02.

BTW... I have actually seen a Linux VM with a problem of answering with "please enter your security code" whenever a call was fwd from any stn, even if a mailbox for that stn did not exist. I had to replace the entire VM.

D

ILE · 05-08-2007, 08:35 AM

Thank you, that worked.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Elitemail CTI LX Lite	MarkIPK	NEC	2	11-08-2006 02:18 AM
Random Hunt List	dbrowder	Meridian Systems	9	10-20-2006 04:37 PM
Random hanging up on pickup?	Shanks	Meridian Systems	3	11-29-2005 12:08 PM
Random LCKO on PRI channels	MTL	Meridian Systems	9	10-14-2005 08:21 AM
ACD reports missing from random queues for 1 hr period durin	M1tech	Meridian Systems	1	01-30-2003 07:39 PM

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)