Think I found the problem, found ext 10 and 11 in dist group 7 and distibution group 1, as well as night cover group. got rid of group 1, and incoming calls appear normal now. Still would like to know the recommended setup for two ext used by operators.
thanks for the reply, I think I will remove both of these extensions and re-program them back in! Is there a recommended way to configure 2 extensions as operators?
After my recent upgrade to (Large) VM which is working fine I have developed a new problem or maybe the system was never setup properly in the beginning. I have two extensions 10 and 11 that act as operators they answer all calls except when AA answers after 6 rings (day) and 1 ring...
I just upgraded my partner acs system to the large vm card. everything went fine except two of the mailboxes one existing and one new one take along time before transferring to VM either from auto attendant or vm transfer the other mailboxes pickup as configured. I have tried to match all the...
I did print the group calling info, nothing is clearly indicating a transfer time or # of rings. What would that item actually be called, or I can post the report?
thanks
My legend with ver 7.0 transfers calls to AA after 5 rings in day mode. I would like to extended that by 1 or 2 more rings. In day mode all calls go to the attendant console on pri trunks pool 70. I think my new winspm 9.0 has me guessing where to change the overflow?
thanks
Using a db9 adapter I built from specs and a com port to hyper terminal, all I get is the report header but no call record data. so I think my connection must be good, but do I have to turn call record output on somehow?
merlin 5.0
My PRI is sending out the correct number for caller ID on the first 17 lines (lines 8125 to 8141) but the last 6 lines (8142-8147) just send the extension number. I made sure the PRI setting is set to send only the line number on all lines, and I made sure the phone number is in place on all...
my cover buttons work fine on my test system, I have a test system on my bench to test programming changes before I apply them to my customer system. I added the dlc's to a new cover group (29) and group cover 29 buttons to the two dlc covers, but they will not ring! I can add a prim cover...
I have seen one ptp with similar intermittent problems once. The solution was to separate tx and rx pairs onto separate cables, due to a long extended dmark run of over 400'
Multiple T1's on a long riser cable will eventually cause odd problems.
I have setup the 2nd and 3rd consoles with group cover and pickup buttons, as you suggested. And picking up calls is working. However, if console 2 or 3 place a call in a park zone or hold. and another call comes in. The cover button will flash but not ring. I think this solution will work but...
Thanks for the reply, this actually is the same question I have listed as a new thread named (Adding Pool S/A Buttons to DLC with PRI) so you can reply under that one if you wish. I have never setup QCC, but the way they use their system is, ALL calls come into 2 DLC consoles then either...
Thanks for the reply TT, I did experiment with a cover button, and while it did work, I was limited to only one button, I couldn't add a couple! The attendants are quite busy with two consoles so I'm trying to give them 4 buttons each to handle incoming calls. Any other thoughts?
thanks
My new PRI is working fine with the main console (100) It has 4 SA buttons and incoming lines roll into them fine. I have 2 other DLC's also with 4 SA buttons. But the calls will not ring into them. I'm not sure why?
The PRI circuit is up and working and calls are ringing into my 4 SA buttons on the main console (100). I have setup the other two consoles (101,138) identically, but incoming calls won't ring there. The main incoming number ports to the T1. is this a DID or ARS issue?
thanks
The PRI is up now, after Qwest rebuilt the trunk group and I removed the extra zero in my outgoing table.
Thanks for everyones responses, this site is invaluable.
I just finished bringing up a Legend on PRI, The C.O. initially was set with NI2 and the D-Channel would not stay up. The protocol change to "custom" is required.
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.