|
|
Joined: Aug 2005
Posts: 2,125
Member
|
Member
Joined: Aug 2005
Posts: 2,125 |
Hey, just a silly thought... Are your bays linked by FIM or by CIM?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
OP
Member
Joined: Jun 2005
Posts: 23 |
Here is the report: Whichever card is set as primary clock source in form 44 will pass clock to the other t-1 card. I recommend making the Telco t-1 primary clock in form 44. The secondary card should not have clock set at the other end (by Asterisk), but you can list it as secondary clock source, in form 44. Only because there are 3 cards, two internal to the Mitel and one in the Asterisk server. Are you recommending that I list the Telco T1 as Primary clock source, the 2nd Mitel T1 as secondary clock source. Then have the Asterisk server treat it's T1 card as a secondary timing source as well? I'll find out about the FIM vs CIM. It's at a remote location.
|
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
OP
Member
Joined: Jun 2005
Posts: 23 |
I am pasting a copy of my problem I asked on the Asterisk user group list just for reference and an insight into my confusion re: timing between all three cards: My Setup looks like this: Mitel 200 SX (1st T1, Bay 1) -------- Bell South
(2nd T1, Bay 2)
|
|
|
Digium TE110P
(T1 Card)
AsteriskMITEL CONFIGURATION Primary Timing Source: 1st T1 Card Secondary Timing Source: 2nd T1 Card ASTERISK CONFIGURATION span=1,1,0,d4,ami (Look to the Span for timing) We are getting a lot of Frame and Slip errors.... Time Slip Frame
7:00 736 950
8:00 690 1200
9:00 437 762
10:00 500 913 ....and then the 2nd Mitel T1 card takes itself offline once the threshold is hit (usually every 18 hours). ?) How can I increase the threshold? What is the proper way to setup timing in this scenario? I have tried setting it both ways: 1) span=1,0,0,d4,ami (Provide timing for the span) 2) span=1,1,0,d4,ami (Look to the Span for timing) And I get the same amount of errors either way. (1) Asterisk set as timing source will cause problems with the 2nd T12 card in Mitel since it will be receiving timing from the Asterisk as well as the 1st T1 card in the Mitel. (2) Asterisk set to expect timing from the Mitel. The 2nd T1 card is expecting timing from the 1st Mitel T1 card and the Asterisk is expecting timing from the 2nd T1 card. Does that sound like it could cause a problem? I don't think the Asterisk server will try to get it's timing from the 1st Mitel T1 and I don't think the 2nd Mitel T1 card will pass along it's timing from the 1st to the Asterisk. I think the solution is to remove the entry in the Mitel that sets the 2nd T1 card as the secondary source for timing. Sound about right? Thanks!
|
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
OP
Member
Joined: Jun 2005
Posts: 23 |
Originally posted by telephoneguy:
Hey, just a silly thought... Are your bays linked by FIM or by CIM? They are connected by Fiber
|
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
OP
Member
Joined: Jun 2005
Posts: 23 |
We had the tech in again today to help out. Still having problems but here's an update:
1) We currently have the telco T1 as the clock source, the 2nd T1 is not listed as a source and the Asterisk T1 card is clocking to the span.
Questions:
1) Where can I find settings for these parameters that can be set in Asterisk:
prewink: Sets the pre-wink timing.
preflash: Sets the pre-flash timing.
wink: Sets the wink timing.
rxwink: Sets the receive wink timing.
rxflash: Sets the receive flash timing.
flash: Sets the flash timing.
start: Sets the start timing.
debounce: Sets the debounce timing.
2) What else can be causing Frame errors and Slip errors?
|
|
|
|
|
Joined: Aug 2005
Posts: 2,125
Member
|
|
Member
Joined: Aug 2005
Posts: 2,125 |
Here is the report:
³ 2 6 1 0 did_trk 20 125 T1 off off avail talkg idle ³ ³ ³ 2 6 16 0 did_trk 35 140 T1 off off avail idle idle ³>³ 2 6 17 0 did_trk 36 off off avail idle idle ³ Sorry, I missed a step. On that screen, scroll down to the affected T-1 or channel, and press 3 (link status). As you'll see, some of the lines are configured differently from the others. We want them all to be E&M but the tech put channels 21-24 as LS/GS. ... We are waiting for the tech to come in and set all 24 channels to E&M wink. That could be your problem. The T-1 needs to amtch what telco is sending. I am not seeing any BPV's just slips and frame errors. I'm not sure what you mean here: Sorry, missed step. Press 3. Only because there are 3 cards, two internal to the Mitel and one in the Asterisk server.
Are you recommending that I list the Telco T1 as Primary clock source, the 2nd Mitel T1 as secondary clock source. Then have the Asterisk server treat it's T1 card as a secondary timing source as well? Yes, that should work. Mitel must get it's signal from telco, but then it will provide it for Asterisk. am pasting a copy of my problem I asked on the Asterisk user group list just for reference and an insight into my confusion re: timing between all three cards: :
Mitel 200 SX (1st T1, Bay 1) -------- Bell South (2nd T1, Bay 2) | | | Digium TE110P (T1 Card) Asterisk
MITEL CONFIGURATION
Primary Timing Source: 1st T1 Card
Secondary Timing Source: 2nd T1 Card
ASTERISK CONFIGURATION
span=1,1,0,d4,ami (Look to the Span for timing) that should be correct, imo. ?) How can I increase the threshold? Form 42 should be t-1 descriptors. Then select esc 8 for options. 1) span=1,0,0,d4,ami (Provide timing for the span)
2) span=1,1,0,d4,ami (Look to the Span for timing) #2, imo. And I get the same amount of errors either way. Time to check other things, such as form 42. (2) Asterisk set to expect timing from the Mitel. The 2nd T1 card is expecting timing from the 1st Mitel T1 card and the Asterisk is expecting timing from the 2nd T1 card.
Does that sound like it could cause a problem? I don't think the Asterisk server will try to get it's timing from the 1st Mitel T1 and I don't think the 2nd Mitel T1 card will pass along it's timing from the 1st to the Asterisk. A PBX only needs one t-1 clock source. It will share with the others. But Southwest Bell must be providing clock. I think the solution is to remove the entry in the Mitel that sets the 2nd T1 card as the secondary source for timing. Sound about right? The secondary clock source only comes into play if the first clock source fails. But it's worth a try... then that rules out a dodgy cable. I assume that bay control cards are seated properly (NOT HOT SWAPPABLE!)?? 1) Where can I find settings for these parameters that can be set in Asterisk:
prewink: Sets the pre-wink timing.
preflash: Sets the pre-flash timing.
wink: Sets the wink timing.
rxwink: Sets the receive wink timing.
rxflash: Sets the receive flash timing.
flash: Sets the flash timing.
start: Sets the start timing.
debounce: Sets the debounce timing. Form 42, ESC 8.
|
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
OP
Member
Joined: Jun 2005
Posts: 23 |
Here is an active channel: ![[Linked Image from members.arstechnica.com]](https://members.arstechnica.com/x/geoffm33/active_channel.png) Here is an inactive channel: ![[Linked Image from members.arstechnica.com]](https://members.arstechnica.com/x/geoffm33/inactive_channel.png) Here is the contents of form 42: ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄ¿
³ [ LINK DESCRIPTOR NUMBER : 2 ] OUTGOING ³ VALUE ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ´
>³ Alarm debounce timer ( 300 - 3200 ms ) ³ 2500 ³<
³ Line Coding ( AMI, AMI&ZCS, B8ZS) ³ AMI ³
³ Line Build Out ( 0, -7.5, -15, -22.5 DB) ³ 0 DB ³
³ Line Length ( max 132, 265, 398, 533 or 655) ³ 0-132 ³
³ Framing ( D4 or ESF ) ³ D4 ³
³ Slip rate - maintenance limit ( 0 - 9000 ) /24 hrs ³ 1000 ³
³ Slip rate - service limit ( 0 - 9000 ) /24 hrs ³ 9000 ³
³ Slip rate - network sync limit ( 0 - 9000 ) /24 hrs ³ 1000 ³
³ BER - maintenance limit ( 10**-n , n = ( 3,4,5,6 )) / hour ³ 4 ³
³ BER - service limit ( 10**-n , n = ( 3,4,5,6 )) / hour ³ 3 ³
³ Framing losses - maintenance limit ( 0 - 9000 ) /24 hrs ³ 1000 ³
³ Framing losses - service limit ( 0 - 9000 ) /24 hrs ³ 9000 ³
³ RTS timer - service limit exceeded ( 1 - 255 min ) ³ 90 ³
³ RTS timer - net slip limit exceeded ( 1 - 255 min ) ³ 90 ³
>³ RTS timer - after alarm ( 0 - 300 sec ) ³ 10 ³
And form 13: ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄ¿
³ [ T1 E&M TRUNK: 3 ] OPTION NAME [SUPERVISION PARAMETER ] ³ STATUS ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄ´
>³ Reverse to Idle ³ NO ³<
³ Far-end gives answer supervision ³ NO ³
³ Inhibit automatic supervision ³ NO ³
³ No seize alarm ³ NO ³
³ No release alarm ³ NO ³
³ Toll office ³ NO ³
³ Is this a CO ³ YES ³
³ DTMF ³ YES ³
³ Save Busy-Out Status ³ NO ³
³ Disconnect timer 150 - 900 ms ( 50 ms inc ) ³ 300 ³
³ Release acknowledge timer 2 - 240 s ( 2 s inc ) ³ 40 ³
³ Guard timer 200 - 1000 ms ( 100 ms inc ) ³ 800 ³
³ Incoming start type ³ WINK ³
³ Debounce timer 20 - 150 ms ( 10 ms inc ) ³ 100 ³
³ Wink timer 150 - 300 ms ( 50 ms inc ) ³ 200 ³
³ Outgoing start type ³ WINK ³
³ Digit outpulsing ratio ³ 60/40 ³
³ Outpulse delay timer 100 - 2000 ms ( 100 ms inc ) ³ 800 ³
³ Flash timer 200 - 700 ms ( 100 ms inc ) ³ 300 ³
>³ Flash type ³LOOP FSH ³<
³ Flash over trunk ³ NO ³
³ Interdigit timer 300 - 800 ms ( 100 ms inc ) ³ 800 ³
³ Wait for delay timer 300 - 5000 ms ( 100 ms inc ) ³ 5000 ³
³ Remote end is a satellite ³ NO ³
³ Remote end is a satellite with OPS lines ³ NO ³
³ Direct access on CO Line Keys: bypass Key System Toll Control ³ NO ³
³ Release Link Trunk ³ NO ³
>³ QSIG Supplementary Services ³ NO ³ Thanks for all the help so far.
|
|
|
|
|
Joined: Jun 2005
Posts: 23
Member
|
|
OP
Member
Joined: Jun 2005
Posts: 23 |
[quote] wink: Sets the wink timing.
flash: Sets the flash timing.
debounce: Sets the debounce timing.But do any of the other settings in form 13 relate to: prewink: Sets the pre-wink timing.
preflash: Sets the pre-flash timing.
rxwink: Sets the receive wink timing.
rxflash: Sets the receive flash timing.
start: Sets the start timing.
|
|
|
|
|
Joined: Aug 2005
Posts: 2,125
Member
|
|
Member
Joined: Aug 2005
Posts: 2,125 |
Start timing is going to be based on E&M Wink emulation, in form 13.
you can set the length of a flash, system-wide, in form 4 (not just for t1) but it's best to leave it alone.
My next step here would be to confirm that the other end (either telco or Asterisk) exactly matches these parameters.
|
|
|
|
|
Joined: Oct 2004
Posts: 1,057
Member
|
|
Member
Joined: Oct 2004
Posts: 1,057 |
Don't get caught up in troubleshooting the wrong problem. The signaling on the trunks "riding" the T1 have nothing to do with slips or "T1" timing errors.
|
|
|
|
Forums84
Topics94,284
Posts638,772
Members49,765
| |
Most Online5,661
May 23rd, 2018
|
|
|
0 members (),
142
guests, and
285
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
