NorstarOption
Technical User
I have 2 COT's that I would like to appear and ring on couple of sets. Do I have to build a separate RDB for each one?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
2 COTs PVR
- Thread starter NorstarOption
- Start date
- Status
No, in fact (much) older releases only allowed one PVR route. You had to use Route 31, or none at all.
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
Good Morning NorstarOption, simply program 2 unused DNs onto the appropriate keys of the telephones in question. Program a standard COT route (LD 16) with AUTO set to YES. In the trunk programming (LD 14), set the ATDN to the DN(s) you programmed on the telephone. This will work for inbound calls. If these are loop start lines, I recommend you have them changed to ground start. If you want to dial out on these lines, you will need to use the route ACOD or setup some TGAR/TARG NCOS programming to use BARS correctly for it.
If he wants the COTs to "appear" on multiple phones, then he is going to need PVRs, otherwise the other appearances will not know of they are in use.
With PVRs, to dial out you just press the button they appear on.
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
With PVRs, to dial out you just press the button they appear on.
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
Sure they will. Example: Phones A and B have DNs 5000 and 5001 programmed as SCR on keys 0 and 1. CO Line 1 has ATDN set to 5000 and CO Line 2 has ATDN set to 5001. When CO Line 1 rings, it will ring both sets on key 0, DN 5000 and will remain lit on both sets when answered.
No, they won't. 5000 and 5001 could be busy on non-trunk calls, incoming or outgoing, and 6599 or 8255 or any other number in the system could be busy on the COT trunk.
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
Don't get me wrong - Auto Terminate might still work fine as telebub points out. Here's something I developed for a customer a few years ago: faq798-6453
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]
GHTROUT, In my example 6599, 8255, or any other number in the system will never access the 2 COT trunks unless they are allowed outbound access via the route ACOD or through BARS.
Example 2 that we have working at a brokerage firm:
They have 4 COT Ground Start trunks for inbound calls. We setup 4 DNs, 5001-5004 on keys 8-11 on 7 or 8 different sets (2616). The ATDN of the 4 COT lines are 5001-5004 respectively and the hunting is performed by the C.O. so no need for LHK in this case. Basically looks like a key system. These sets do not access these lines for outbound, they grab key 0, dial 9, and use the normal PRIs.
Call comes into the 1st COT line and rings all sets on key 8. User answers and key 8 remains lit as busy on all sets. Next call comes in and hunts to 2nd CO Line which rings to key 9. It is answered and remains lit on key 9 of all sets in the group. Works great.
If these 4 lines were needed to be used for outbound, then it throws a kink in it but would still work although the correlation may be wrong. If the user grabbed key 8, DN 5001, and dialed out using the route ACOD, they would grab the 4th COT (using linear sequence) which is programmed to ring in on key 11. But the users will still see 5001 lit up as busy on all sets in the group. LHK would have to be 11 for this to work properly as well. You could also train the users to start their outbound calls with key 11 so the correlation matches. If the user grabbed key 0 and made the same call, then yes all DNs on keys 8-11 will be dark and no one will know the line is tied up.
And I may be way overthinking what NorstarOption wants to do but I'm just giving a setup we have working currently that sounds like what he is after.
War Eagle!!
Example 2 that we have working at a brokerage firm:
They have 4 COT Ground Start trunks for inbound calls. We setup 4 DNs, 5001-5004 on keys 8-11 on 7 or 8 different sets (2616). The ATDN of the 4 COT lines are 5001-5004 respectively and the hunting is performed by the C.O. so no need for LHK in this case. Basically looks like a key system. These sets do not access these lines for outbound, they grab key 0, dial 9, and use the normal PRIs.
Call comes into the 1st COT line and rings all sets on key 8. User answers and key 8 remains lit as busy on all sets. Next call comes in and hunts to 2nd CO Line which rings to key 9. It is answered and remains lit on key 9 of all sets in the group. Works great.
If these 4 lines were needed to be used for outbound, then it throws a kink in it but would still work although the correlation may be wrong. If the user grabbed key 8, DN 5001, and dialed out using the route ACOD, they would grab the 4th COT (using linear sequence) which is programmed to ring in on key 11. But the users will still see 5001 lit up as busy on all sets in the group. LHK would have to be 11 for this to work properly as well. You could also train the users to start their outbound calls with key 11 so the correlation matches. If the user grabbed key 0 and made the same call, then yes all DNs on keys 8-11 will be dark and no one will know the line is tied up.
And I may be way overthinking what NorstarOption wants to do but I'm just giving a setup we have working currently that sounds like what he is after.
War Eagle!!
- Thread starter
- #9
NorstarOption
Technical User
I'll do PVR, just making sure I dont have to build RDB for each one.
you do know with pvr, the dn is not dialable.. i have one on my set.. sorta strange, no dial 9.. just a private number.. just set the prdn on the trunk to match the pvr xxxx on the set... here's my trunk
the only change on the set is key 4 pvr 8997.. btw 8997 stayed in the ludn table.. but it will not assign
john poole
bellsouth business
columbia,sc
Code:
DES PVR
TN 004 0 15 03
TYPE COT
CDEN 8D
CUST 0
XTRK XUT
TIMP 600
BIMP 3COM
TRK ANLG
NCOS 1
RTMB 62 2
PRDN 8997
CMF NO
SIGL LOP
SUPN NO
AST NO
IAPG 0
CLS UNR DTN CND ECD WTA LPR APN THFD SPCD
P10 NTC
TKID
AACR NO
DATE NO DATEthe only change on the set is key 4 pvr 8997.. btw 8997 stayed in the ludn table.. but it will not assign
john poole
bellsouth business
columbia,sc
- Status
Similar threads
- Question