P2P T1 on networked Legend

[FordMan77]

I have 2 Legends that are networked together via a straight p2p T1. I have all the prog. in place (non-lcl udp, trunks, etc...). I have made calls from the remote site to the main site with no problem. When I try to make a call from the main to remote site, all I get is silence, and occasionally it just drops the trunk altogether. When I dial my remote site, I see the amber light come up on the 100D card but the call never completes. If I stay on the line long enough I hear screeching occasionally. Anyone know what could be a possible cause?

 

[glg01]

I would start by printing out the PRI info of both ends to confirm all programming looks good. It sounds like when you try to dial the other end from the main location that you hit dead air meaning some kind of mapping/routing issue. lg

 

[FordMan77]

This is a non-PRI T1, so nothing to look at there. I'm thinking it may be a clocking issue. As I have it set now, the remote site is set to Loop, and the main site is set to local.

 

[TouchToneTommy]

Even though it is a straight 24-channel point-to-point T1, you should set your switches up as PRI, so the D-channel is used to communicate with each other.

 

[glg01]

The PRI software in the Legend/Magix is communicating in p2p setups. That is how centralized voice mail and other features work between the two systems. Print out the PRI information for both locations and maybe we can help you get this fixed. Your are right they both have to be set for loop on the timing and as always if you have other T-1's in these systems you should time off of the networks T-1's first. lg

 

[glg01]

Okay wait a minute you don't HAVE to use the PRI. If you do use the Tie Lines type T-1 settings between these be sure the switch identifiers are set right for the tie trunks you have in the pools for the p2p. In this case print out the T-1 info and the Tie Line info and verify the programming. lg

 

[dagwoodsystems]

Print PRI info as suggested. On one end, you should see "Switch" set as MERLIN-Ntwk, on the other will show MERLIN-PBX.

Confirm that a T1 printout shows both ends as B8ZS/ESF using DMI-MOS signalling.

A printout of Trunk Group (General) should reveal the External Switch ID...most likely set as 21 on one end, and 22 on the other.

Take a look at those reports and post any decrepancies.


Tim Alberstein

http://www.dagwoodsystems.com

 

[Pepperz]

If Dagwoodsystems post doesn't do it, try swapping the two cards and see where the problem shows up. This way, you rule out the cards.

 

[dagwoodsystems]

And if I wasn't clear before, I am aware (as you are) that this is a non-PRI T1. Setting a straight point-to-point T1 for the purposes of networking two Legends/Magix together ultimately uses a tweaked flavor if PRI, but it's not programmed as a PRI would normally be. I explained some of that in

http://www.tek-tips.com/viewthread.cfm?qid=1392833.

However, some of those PRI reports will come in handy.

As I was reading this post again, your statement about screeching got my attention. Clicks, pops, screeches and disconnects on digital circuits are almost always one of several things: either a mismatched number of channels end to end (perhaps the D-Channel got snuck in accidentally in your trunk programming), network synchronization is wrong or there exists some physical layer problem, which you can check by looking at the T1 error stats. Look for slips, bipolar violations and other such errors.

Tim Alberstein

http://www.dagwoodsystems.com

 

[FordMan77]

Ok, got info from both switches and this is what I have: PRI report for both is blank, so nothing to show there. The trunk group is indeed set for 21 on the main site, and 22 at the remote. And below is the T1 print from both sites.

Main Site-DS1 INFORMATION

A DS1 SLOT ATTRIBUTES

A Slot Type Format Supp Signal LineComp
A 1 T1 ESF B8ZS Rob_Bit 1



Remote Site- DS1 INFORMATION

A DS1 SLOT ATTRIBUTES

A Slot Type Format Supp Signal LineComp
A 2 T1 ESF B8ZS Rob_Bit 1

 

[dagwoodsystems]

If you want to do true networking, then you've got some more programming to do.

Otherwise, the best you'll do with what you've got is closer to ordinary tie lines. That means dialing an access code, then the remote extension number. Centralized voicemail doesn't work over tie lines either.

With things like non-local UDP parameters and switch identifiers already in place, it seems that you want to go with the integrated private network solution. In order to make that happen, you've got to complete the PRI portion of the programming. Again, forget what you already know about PRI. Point-to-point vanilla T1s are built as PRI when networking Magix and/or Legends.

Would you like a programming reference or a cheat sheet?

Tim Alberstein

http://www.dagwoodsystems.com

 

[glg01]

He can utilize the UDP routing using tie lines and not have to dial an access code....but there are definite benefits by running the Legend Ntwk PRI setup. He says he can dial one direction but not the other....and this is what he needs help with. Are you using CSU/DSU's? It is almost like he accesses the T-1 channel from the non-working end and doesn't make it to the other end which still could be a mapping issue. You need to figure out which channel you can complete you call on from the one end and then be sure that same channel is the one you use from the other end and retest. In other words only put that good channel in the pool just to see if your test call can go through. If you are able to complete your call both ways on the one channel then you would know it has to be a mapping issue. We really need to see a little more info on your programming. lg

 

[FordMan77]

What kind of info would you like to see? I have info already saved from both sites, and I have a full sys. print of both. I will be pulling a fresh sys print of both sites soon so I can try and figure this one out.

 

[glg01]

Let's call the main site Node 1 (N1) and remote site Node 2 (N2). Since you have programmed both of these and you are able to make a call from N2 to N1 that tells me you are not new at this...so let's start with a basic question. In N2 do you have any modules with TTR's in them? You say when placing your call from N1 to N2 it fails but lights the 100D card and does nothing. It could be your programming is okay but you will need TTR's in N2 to complete the call kind of like DNIS digits being sent off any other Tie Line T-1. So just post your System Setup for N1 and N2 for now. lg

 

[FordMan77]

Sys Setup N1:

SYSTEM INFORMATION


A Current Date: 09/20/07
A Current Time: 13:49:36

A System : Mode AutoMaintBusy AutoBusyTie
A : Hybrid/PBX Disable Disable

A Language: SystemLang SMDR Printer
A English English English

A CTI Links :
A Direct Line Operators : 2100 2107
A Queued Call Operators :
A SysProg Port : 2100 Password : craftr4

A Transfer : Type Audible OneTouch(Complete) ReturnTimer
A : Ring MusicOnHold Transfer(Auto) 8 rings

A VMS Transfer Return Interval : 4
A Paging System Lines :
A Music On Hold Line :
A Camp On Time : 90 sec
A Call Park Return Time : 180 sec
A Auto Callback Rings : 3
A Extension Status (ESS) : Group Call / CMS
A ESS Operators :

A SMDR: Min.CallTime CallReport Format UDP
A : 40 sec In/Out Basic In/Out

A Intercom Dial Tone : Inside
A Reminder Service Cancel : :

A Behind Switch Code : Drop Transfer Conference
A :

A Inter-digit Timers (seconds) : 5 24 24 10 10 10 10 5 5
A Recall Timer : 450 msec
A Second Dial-tone Timer : 0 msec
A Rotary Line Cut Through : Delay
A Unassigned Extension : 2100

A Automatic Backup : Weekly - 02:00 Sunday

A T1/PRI/BRI Clock Synchronization:
A Primary Secondary Tertiary
A 1/0 Local

A Slot # 1: 100D
A Slot # 2: 800 GS/LS
A Slot # 3: 408 GLM-U
A Slot # 4: 008 MLX-U
A Slot # 5: 012
A Slot # 6: Not Used
A Slot # 7: Not Used
A Slot # 8: Not Used
A Slot # 9: Not Used
A Slot # 10: Not Used
A Slot # 11: Not Used
A Slot # 12: Not Used
A Slot # 13: Not Used
A Slot # 14: Not Used
A Slot # 15: Not Used
A Slot # 16: Not Used
A Slot # 17: Not Used


Sys Setup N2:

SYSTEM INFORMATION


A Current Date: 09/20/07
A Current Time: 13:45:56

A System : Mode AutoMaintBusy AutoBusyTie
A : Hybrid/PBX Disable Disable

A Language: SystemLang SMDR Printer
A English English English

A CTI Links :
A Direct Line Operators : 6100 6104
A Queued Call Operators :
A SysProg Port : 6100 Password : craftr4

A Transfer : Type Audible OneTouch(Complete) ReturnTimer
A : Ring MusicOnHold Transfer(Auto) 4 rings

A VMS Transfer Return Interval : 4
A Paging System Lines :
A Music On Hold Line :
A Camp On Time : 90 sec
A Call Park Return Time : 180 sec
A Auto Callback Rings : 3
A Extension Status (ESS) : Group Call / CMS
A ESS Operators :

A SMDR: Min.CallTime CallReport Format UDP
A : 40 sec In/Out Basic In/Out

A Intercom Dial Tone : Inside
A Reminder Service Cancel : :

A Behind Switch Code : Drop Transfer Conference
A :

A Inter-digit Timers (seconds) : 5 24 24 10 10 10 10 5 5
A Recall Timer : 450 msec
A Second Dial-tone Timer : 0 msec
A Rotary Line Cut Through : Delay
A Unassigned Extension : 6100

A Automatic Backup : Weekly - 02:00 Sunday

A T1/PRI/BRI Clock Synchronization:
A Primary Secondary Tertiary
A 2/1 Loop

A Slot # 0: CKE4 CPU
A Slot # 1: 408 GS/LS-MLX
A Slot # 2: 100D
A Slot # 3: Not Used
A Slot # 4: Not Used
A Slot # 5: Not Used
A Slot # 6: Not Used
A Slot # 7: Not Used
A Slot # 8: Not Used
A Slot # 9: Not Used
A Slot # 10: Not Used
A Slot # 11: Not Used
A Slot # 12: Not Used
A Slot # 13: Not Used
A Slot # 14: Not Used
A Slot # 15: Not Used
A Slot # 16: Not Used
A Slot # 17: Not Used

 

[FordMan77]

Now that you mention TTR's, from what I can tell I have 4 TTR's in N1, and none in N2. You may want to verify this as the list I have showing TTR modules is old.

 

[glg01]

There are no TTR's in N2. That is why N1 can't call N2. It doesn't take TTR's for MLX sets to make a call. Put a module in N2 that has TTR's and I believe you will be able to place calls between N1 and N2. lg

 

[Pepperz]

It takes TTR's to receive a call over this kind of network..... been there couldn't do that, until I put in an 016 T/R or something like that.

 

[glg01]

I know it takes TTR's If he has a 400GS/LS(4TTR)trunk module that would probably be his cheapest module since that is the reason they were made to start with. If he has modules laying around the office then I would recommend some module with 4TTR's in it....he could remove the 012 module in N1 and take it to N2 for testing purposes just to prove this is the reason he can't call between N1 and N2. Once he proves this is indeed the problem then he can purchase what he wants. lg

 

[FordMan77]

I could remove the 012 module, but I think they may miss having thier VM, as its an 007MLM. They have a spare 016 mod laying around that I can install in the remote site and test, but I'll bet this is the issue.

Then it's on to giving the remote site VM coverage. At least the doc seems pretty clear on that subject.