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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Branch office call routing - broke

Status
Not open for further replies.

bryandj23

IS-IT--Management
Aug 18, 2003
105
US
Hi All. Hopefully someone can point me in the right direction on this. Last month, we broke a portion of our point to point T1 line to handle both Voice and Data. The data portion of this project has been successful.

Our branch office is configured so that incoming calls are routed to our main office receptionist at Ext. 110 through the T1. On her 4422 phone, calls to our main office show on the line buttons, while calls coming in from the branch office show up on the left hand side (SA buttons, I believe), and the display will say "MIDLAND 772".

I was notified that calls from our branch aren't reaching our main office. Checking SMDR reports, it appears that a call hasn't been logged on the 8201 line in over a month!

I headed to the branch to investigate any line problems, and did find a loose RJ11 on one of the lines. I was able to call our branch office's main number and reach our receptionist at the main office. I figured the loose connection was the culprit, until I came into work today.
(I think I was able to reach her because I was actually on our main trunk phone number).

I ran a new PRINT ALL report, comparing it to a report created back in 2006 (before we split the T1). The only differences I could see is that now the CSU is configured with channels; whereas before it was blank:

A Slot 3
A CSU: Activated
A Assigned Channels: 06 07 08 09 10 11 12 13
A 14 15 16 17 18 19 20 21
A 22 23
A DSU: Activated
A Data Port 1
A Receive Clock: DTE
A Invert Transmit Clock: No
A Invert Receive Clock: No
A Invert Transmit Data: No
A Invert Receive Data: No
A Rate: 64 kbps
A Assigned Channels: 06 07 08 09 10 11 12 13
A 14 15 16 17 18 19 20 21
A 22 23


The channels above represent what we're using on the T1 for data. Is this an incorrect configuration? Should the DATA channels be on the DSU and the VOICE channels be on the CSU?

FWIW, "Data Channel Selection" under Lines/Trunks->CSU/DSU shows channels 1 through 5 on "Switch" (as well as channel 24), and channels 6 through 23 on "router".

If any other information may be needed, I'll provide it as quickly as possible.

Thanks very much!
 
A few other thoughts....

My PRI configuration still shows "22" for "Extern Switch" under all of the channels that make up our PRI. Should this be changed for the channels that are now doing data?

A GENERAL TRUNK INFORMATION


A QCC QCC Extern
A Trk SS/PP RemAccess Pool TlPrfx HldDisc Principal Prty Oper Switch
A 8201 2/ 1 No Remote Yes Long 4
A 8202 2/ 2 No Remote 60 Yes Long 4
A 8203 2/ 3 No Remote 60 Yes Long 4
A 8204 2/ 4 No Remote 60 Yes Long 4
A 8205 2/ 5 No Remote 60 Yes Long 4
A 8206 2/ 6 No Remote Yes Long 4
A 8207 2/ 7 No Remote Yes Long 4
A 8208 2/ 8 No Remote Yes Long 4
A 8209 3/ 1 No Remote 891 Yes Long 4 22
A 8210 3/ 2 No Remote 891 Yes Long 4 22
A 8211 3/ 3 No Remote 891 Yes Long 4 22
A 8212 3/ 4 No Remote 891 Yes Long 4 22
A 8213 3/ 5 No Remote 891 Yes Long 4 22
A 8214 3/ 6 No Remote Yes Long 4 22
A 8215 3/ 7 No Remote Yes Long 4 22
A 8216 3/ 8 No Remote Yes Long 4 22
A 8217 3/ 9 No Remote Yes Long 4 22
A 8218 3/10 No Remote Yes Long 4 22
A 8219 3/11 No Remote Yes Long 4 22
A 8220 3/12 No Remote Yes Long 4 22
A 8221 3/13 No Remote Yes Long 4 22
A 8222 3/14 No Remote Yes Long 4 22
A 8223 3/15 No Remote Yes Long 4 22
A 8224 3/16 No Remote Yes Long 4 22
A 8225 3/17 No Remote Yes Long 4 22
A 8226 3/18 No Remote Yes Long 4 22
A 8227 3/19 No Remote Yes Long 4 22
A 8228 3/20 No Remote Yes Long 4 22
A 8229 3/21 No Remote Yes Long 4 22
A 8230 3/22 No Remote Yes Long 4 22
A 8231 3/23 No Remote Yes Long 4 22
A 8232 3/24 No Remote Yes Long 4
A 8233 0/ 0 No Remote Yes Long 4
A 8234 0/ 0 No Remote Yes Long 4
A 8235 0/ 0 No Remote Yes Long 4
A 8236 0/ 0 No Remote Yes Long 4
A 8237 0/ 0 No Remote Yes Long 4
A 8238 0/ 0 No Remote Yes Long 4
A 8239 0/ 0 No Remote Yes Long 4
A 8240 0/ 0 No Remote Yes Long 4
A 8241 0/ 0 No Remote Yes Long 4
A 8242 0/ 0 No Remote Yes Long 4
A 8243 0/ 0 No Remote Yes Long 4
A 8244 0/ 0 No Remote Yes Long 4
A 8245 0/ 0 No Remote Yes Long 4
A 8246 0/ 0 No Remote Yes Long 4
A 8247 0/ 0 No Remote Yes Long 4
A 8248 0/ 0 No Remote Yes Long 4
A 8249 0/ 0 No Remote Yes Long 4
A 8250 0/ 0 No Remote Yes Long 4
A 8251 0/ 0 No Remote Yes Long 4
A 8252 0/ 0 No Remote Yes Long 4
A 8253 0/ 0 No Remote Yes Long 4
A 8254 0/ 0 No Remote Yes Long 4
A 8255 0/ 0 No Remote Yes Long 4



A Slot 3 Switch: MERLIN-PBX

A System: By line

A BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
A 80 3 ElecTandNtwk Route Directly to UDP

A Channel ID: 1 2 3 4 5

A Line PhoneNumber NumberToSend
A 8209
A 8210
A 8211
A 8212
A 8213



Lines 8209-8213 should be for Voice, while 8214-8230 are Data. 8231 is then the D-Channel. Now, should those "22's" for external switch be removed?
 
Disregard. It MUST be an issue with that particular line/wiring/etc, since digging further into SMDR data reveals that calls are in fact routing back and forth.

Road Trip.
 
Welp, found my problem.

When I was breaking out the T1, I removed the main trunk (8201) out of the main pool (60). While subsequent lines within our hunt group would route over the T1, the 8201 trunk would not because the pool is tied to a coverage group which then routes calls to the T1.

Added 8201 to pool 60 and all is good.

Does this make sense?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top