thr3ads.net - asterisk users - [asterisk-users] One PRI card with 2 (or more) Telcos [Mar 2011]

If this information is useful, please help other people find it:
Share via:

Tiago Geada

2011-Mar-18 17:52 UTC

[asterisk-users] One PRI card with 2 (or more) Telcos

Hi list!

We currently have a PRI gateway composed by a box with two Digium quad-span
PRI cards (a TE420 and a ).
One of the cards is filled with TELCO1, while the other has first two slots
filled with TELCO2, and 3rd slot with TELCO3.

I am currently having (timer ?) issues on TELCO3 (span 7)

D-Chan (202 as determined by dahdi_genconf ) is constantly failing causing
on-going calls to terminate.
Problem clears immediately tho. I send a copy of the log with pri debug at a
time of problems...

Is there a problem having 2 telcos on the same PRI card?
Would somebody help?

asterisk*CLI> pri show span 7
Primary D-channel: 202
Status: Provisioned, Up, Active
Switchtype: EuroISDN
Type: CPE
Overlap Dial: 0
Logical Channel Mapping: 0
Timer and counter settings:
  N200: 3
  N202: 3
  K: 7
  T200: 1000
  T202: 10000
  T203: 10000
  T303: 4000
  T305: 30000
  T308: 4000
  T309: 6000
  T313: 4000
  T-HOLD: 4000
  T-RETRIEVE: 4000
  T-RESPONSE: 4000
Overlap Recv: No


and

[Mar 18 17:04:05] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (I): T200
expired N200 times sending RR/RNR in state 8(Timer recovery)
[Mar 18 17:04:05] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:05] VERBOSE[19844] chan_dahdi.c: Changing from state 8(Timer
recovery) to 5(Awaiting establishment)
[Mar 18 17:04:06] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:07] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:08] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): *T200
expired N200 times sending SABME in state 5(Awaiting establishment)*
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Changing from state
5(Awaiting establishment) to 4(TEI assigned)
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
Q931_DL_EVENT_DL_RELEASE_IND(3)
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Start T309 for call cref=56
on channel 2
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Start T309 for call cref=64
on channel 3
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Start T309 for call cref=58
on channel 4
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Start T309 for call cref=66
on channel 6
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
assigned) to 5(Awaiting establishment)
[Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c:   == Primary D-Channel on
span 7 down
[Mar 18 17:04:09] WARNING[19844] chan_dahdi.c: No D-channels available!
 Using Primary channel 202 as D-channel anyway!
[Mar 18 17:04:10] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:11] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:12] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): T200
expired N200 times sending SABME in state 5(Awaiting establishment)
[Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: Changing from state
5(Awaiting establishment) to 4(TEI assigned)
[Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
Q931_DL_EVENT_DL_RELEASE_IND(3)
[Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
assigned) to 5(Awaiting establishment)
[Mar 18 17:04:13] WARNING[19844] chan_dahdi.c: No D-channels available!
 Using Primary channel 202 as D-channel anyway!
[Mar 18 17:04:14] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: T309 timed out waiting for
data link re-establishment
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: q931.c:7750
pri_internal_clear: Call 56 enters state 0 (Null).  Hold state: Idle
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: clearing, alive 1, hangupack
0
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:   == Primary D-Channel on
span 7 up
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:     -- Channel 0/2, span 7
got hangup, cause 27
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: T309 timed out waiting for
data link re-establishment
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: q931.c:7750
pri_internal_clear: Call 64 enters state 0 (Null).  Hold state: Idle
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: clearing, alive 1, hangupack
0
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:     -- Channel 0/3, span 7
got hangup, cause 27
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: T309 timed out waiting for
data link re-establishment
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: q931.c:7750
pri_internal_clear: Call 58 enters state 0 (Null).  Hold state: Idle
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: clearing, alive 1, hangupack
0
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:     -- Channel 0/4, span 7
got hangup, cause 27
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: T309 timed out waiting for
data link re-establishment
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: q931.c:7750
pri_internal_clear: Call 66 enters state 0 (Null).  Hold state: Idle
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: clearing, alive 1, hangupack
0
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:     -- Channel 0/6, span 7
got hangup, cause 27
[Mar 18 17:04:15] VERBOSE[27353] pbx.c:   == Spawn extension (incoming-pri,
sw-30-218543080, 11) exited non-zero on 'DAHDI/189-1'
[Mar 18 17:04:15] VERBOSE[27353] chan_dahdi.c: q931_hangup: other hangup
[Mar 18 17:04:15] VERBOSE[27354] app_mixmonitor.c:   == MixMonitor close
filestream
[Mar 18 17:04:15] VERBOSE[27353] chan_dahdi.c: NEW_HANGUP DEBUG: Calling
q931_hangup, ourstate Null, peerstate Null, hold-state Idle
[Mar 18 17:04:15] VERBOSE[27353] chan_dahdi.c: NEW_HANGUP DEBUG: Destroying
the call, ourstate Null, peerstate Null, hold-state Idle
[Mar 18 17:04:15] VERBOSE[27353] chan_dahdi.c:     -- Hungup
'DAHDI/189-1'
[Mar 18 17:04:15] VERBOSE[27354] app_mixmonitor.c:   == Executing
[/usr/local/bin/mixmon "1300465595.27894_withhold.gsm"
"/var/log/asterisk/asterisk_rec/218543080/2011-03-18"]
[Mar 18 17:04:15] VERBOSE[27279] pbx.c:   == Spawn extension (incoming-pri,
sw-30-218543080, 11) exited non-zero on 'DAHDI/188-1'
[Mar 18 17:04:15] VERBOSE[27279] chan_dahdi.c: q931_hangup: other hangup
[Mar 18 17:04:15] VERBOSE[27279] chan_dahdi.c: NEW_HANGUP DEBUG: Calling
q931_hangup, ourstate Null, peerstate Null, hold-state Idle
[Mar 18 17:04:15] VERBOSE[27279] chan_dahdi.c: NEW_HANGUP DEBUG: Destroying
the call, ourstate Null, peerstate Null, hold-state Idle
[Mar 18 17:04:15] VERBOSE[27280] app_mixmonitor.c:   == MixMonitor close
filestream
[Mar 18 17:04:15] VERBOSE[27279] chan_dahdi.c:     -- Hungup
'DAHDI/188-1'
[Mar 18 17:04:15] VERBOSE[27280] app_mixmonitor.c:   == Executing
[/usr/local/bin/mixmon "1300465487.27876_219575683.gsm"
"/var/log/asterisk/asterisk_rec/218543080/2011-03-18"]
[Mar 18 17:04:15] VERBOSE[27954] pbx.c:   == Spawn extension (incoming-pri,
sw-30-218543080, 11) exited non-zero on 'DAHDI/192-1'
[Mar 18 17:04:15] VERBOSE[27955] app_mixmonitor.c:   == MixMonitor close
filestream
[Mar 18 17:04:15] VERBOSE[27954] chan_dahdi.c: q931_hangup: other hangup
[Mar 18 17:04:15] VERBOSE[27954] chan_dahdi.c: NEW_HANGUP DEBUG: Calling
q931_hangup, ourstate Null, peerstate Null, hold-state Idle
[Mar 18 17:04:15] VERBOSE[27954] chan_dahdi.c: NEW_HANGUP DEBUG: Destroying
the call, ourstate Null, peerstate Null, hold-state Idle
[Mar 18 17:04:15] VERBOSE[27954] chan_dahdi.c:     -- Hungup
'DAHDI/192-1'
[Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:15] VERBOSE[27955] app_mixmonitor.c:   == Executing
[/usr/local/bin/mixmon "1300467477.28066_229959499.gsm"
"/var/log/asterisk/asterisk_rec/218543080/2011-03-18"]
[Mar 18 17:04:15] VERBOSE[27487] pbx.c:   == Spawn extension (incoming-pri,
sw-30-218543080, 11) exited non-zero on 'DAHDI/190-1'
[Mar 18 17:04:15] VERBOSE[27487] chan_dahdi.c: q931_hangup: other hangup
[Mar 18 17:04:15] VERBOSE[27488] app_mixmonitor.c:   == MixMonitor close
filestream
[Mar 18 17:04:15] VERBOSE[27487] chan_dahdi.c: NEW_HANGUP DEBUG: Calling
q931_hangup, ourstate Null, peerstate Null, hold-state Idle
[Mar 18 17:04:15] VERBOSE[27487] chan_dahdi.c: NEW_HANGUP DEBUG: Destroying
the call, ourstate Null, peerstate Null, hold-state Idle
[Mar 18 17:04:15] VERBOSE[27487] chan_dahdi.c:     -- Hungup
'DAHDI/190-1'
[Mar 18 17:04:15] VERBOSE[27488] app_mixmonitor.c:   == Executing
[/usr/local/bin/mixmon "1300466049.27932_263949634.gsm"
"/var/log/asterisk/asterisk_rec/218543080/2011-03-18"]
[Mar 18 17:04:16] VERBOSE[27280] app_mixmonitor.c:   == End MixMonitor
Recording DAHDI/188-1
[Mar 18 17:04:16] VERBOSE[27488] app_mixmonitor.c:   == End MixMonitor
Recording DAHDI/190-1
[Mar 18 17:04:16] VERBOSE[27354] app_mixmonitor.c:   == End MixMonitor
Recording DAHDI/189-1
[Mar 18 17:04:16] VERBOSE[27955] app_mixmonitor.c:   == End MixMonitor
Recording DAHDI/192-1
[Mar 18 17:04:16] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): T200
expired N200 times sending SABME in state 5(Awaiting establishment)
[Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: Changing from state
5(Awaiting establishment) to 4(TEI assigned)
[Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
Q931_DL_EVENT_DL_RELEASE_IND(3)
[Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
assigned) to 5(Awaiting establishment)
[Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c:   == Primary D-Channel on
span 7 down
[Mar 18 17:04:17] WARNING[19844] chan_dahdi.c: No D-channels available!
 Using Primary channel 202 as D-channel anyway!
[Mar 18 17:04:18] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:19] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:20] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): T200
expired N200 times sending SABME in state 5(Awaiting establishment)
[Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: Changing from state
5(Awaiting establishment) to 4(TEI assigned)
[Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
Q931_DL_EVENT_DL_RELEASE_IND(3)
[Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
assigned) to 5(Awaiting establishment)
[Mar 18 17:04:21] WARNING[19844] chan_dahdi.c: No D-channels available!
 Using Primary channel 202 as D-channel anyway!
[Mar 18 17:04:22] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:23] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:24] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): T200
expired N200 times sending SABME in state 5(Awaiting establishment)
[Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: Changing from state
5(Awaiting establishment) to 4(TEI assigned)
[Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
Q931_DL_EVENT_DL_RELEASE_IND(3)
[Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
assigned) to 5(Awaiting establishment)
[Mar 18 17:04:25] WARNING[19844] chan_dahdi.c: No D-channels available!
 Using Primary channel 202 as D-channel anyway!
[Mar 18 17:04:26] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:27] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
[Mar 18 17:04:28] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110318/e27ea435/attachment.htm>

Tiago Geada

2011-Mar-18 18:15 UTC

head link

[asterisk-users] One PRI card with 2 (or more) Telcos

Just a follow up with a bit more information

asterisk*CLI> module show like timing
Module                         Description                              Use
Count
res_timing_pthread.so          pthread Timing Interface                 0

*res_timing_dahdi.so            DAHDI Timing Interface
  40*
2 modules loaded
asterisk*CLI>


--

 [root at asterisk ~]# dahdi_test -c 100

Opened pseudo dahdi interface, measuring accuracy...

99.999% 99.999% 99.992% 99.997% 99.998% 99.995% 99.998% 99.996%

99.997% 99.998% 99.997% 99.994% 99.991% 99.999% 99.998% 99.998%

99.995% 99.993% 99.998% 99.999% 99.998% 99.995% 99.992% 99.998%

100.000% 99.998% 99.995% 99.992% 99.999% 99.998% 99.998% 99.999%

99.995% 99.999% 99.999% 99.998% 99.999% 99.997% 99.999% 99.998%

99.998% 99.996% 99.992% 99.998% 99.998% 99.999% 99.996% 99.992%

99.999% 99.998% 99.997% 99.997% 99.997% 99.998% 99.995% 99.994%

99.995% 99.992% 99.999% 99.993% 99.990% 99.995% 99.993% 99.999%

99.997% 99.993% 99.999% 99.996% 99.998% 99.996% 99.993% 99.995%

99.992% 99.998% 99.993% 99.993% 99.999% 99.993% 99.998% 99.996%

99.993% 99.996% 99.996% 99.994% 99.999% 99.996% 99.996% 99.992%

99.999% 99.996% 99.991% 99.996% 99.992% 99.998% 99.997% 99.994%

99.998% 99.995%

--- Results after 98 passes ---

Best: 100.000 -- Worst: 99.990 -- Average: 99.996163, Difference: 99.998235


--

 [root at asterisk ~]# cat
/sys/devices/system/clocksource/clocksource0/current_clocksource
*tsc*
 [root at asterisk ~]# cat
/sys/devices/system/clocksource/clocksource0/available_clocksource
tsc hpet acpi_pm jiffies


On 18 March 2011 17:52, Tiago Geada <tiago.geada at gmail.com> wrote:
> Hi list!
>
> We currently have a PRI gateway composed by a box with two Digium quad-span
> PRI cards (a TE420 and a ).
> One of the cards is filled with TELCO1, while the other has first two slots
> filled with TELCO2, and 3rd slot with TELCO3.
>
> I am currently having (timer ?) issues on TELCO3 (span 7)
>
> D-Chan (202 as determined by dahdi_genconf ) is constantly failing causing
> on-going calls to terminate.
> Problem clears immediately tho. I send a copy of the log with pri debug at
> a time of problems...
>
> Is there a problem having 2 telcos on the same PRI card?
> Would somebody help?
>
> asterisk*CLI> pri show span 7
> Primary D-channel: 202
> Status: Provisioned, Up, Active
> Switchtype: EuroISDN
> Type: CPE
> Overlap Dial: 0
> Logical Channel Mapping: 0
> Timer and counter settings:
>   N200: 3
>   N202: 3
>   K: 7
>   T200: 1000
>   T202: 10000
>   T203: 10000
>   T303: 4000
>   T305: 30000
>   T308: 4000
>   T309: 6000
>   T313: 4000
>   T-HOLD: 4000
>   T-RETRIEVE: 4000
>   T-RESPONSE: 4000
> Overlap Recv: No
>
>
> and
>
> [Mar 18 17:04:05] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (I): T200
> expired N200 times sending RR/RNR in state 8(Timer recovery)
> [Mar 18 17:04:05] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:05] VERBOSE[19844] chan_dahdi.c: Changing from state 8(Timer
> recovery) to 5(Awaiting establishment)
> [Mar 18 17:04:06] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:07] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:08] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): *T200
> expired N200 times sending SABME in state 5(Awaiting establishment)*
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Changing from state
> 5(Awaiting establishment) to 4(TEI assigned)
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
> Q931_DL_EVENT_DL_RELEASE_IND(3)
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Start T309 for call cref=56
> on channel 2
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Start T309 for call cref=64
> on channel 3
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Start T309 for call cref=58
> on channel 4
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Start T309 for call cref=66
> on channel 6
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
> assigned) to 5(Awaiting establishment)
> [Mar 18 17:04:09] VERBOSE[19844] chan_dahdi.c:   == Primary D-Channel on
> span 7 down
> [Mar 18 17:04:09] WARNING[19844] chan_dahdi.c: No D-channels available!
>  Using Primary channel 202 as D-channel anyway!
> [Mar 18 17:04:10] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:11] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:12] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): T200
> expired N200 times sending SABME in state 5(Awaiting establishment)
> [Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: Changing from state
> 5(Awaiting establishment) to 4(TEI assigned)
> [Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
> Q931_DL_EVENT_DL_RELEASE_IND(3)
> [Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:13] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
> assigned) to 5(Awaiting establishment)
> [Mar 18 17:04:13] WARNING[19844] chan_dahdi.c: No D-channels available!
>  Using Primary channel 202 as D-channel anyway!
> [Mar 18 17:04:14] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: T309 timed out waiting for
> data link re-establishment
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: q931.c:7750
> pri_internal_clear: Call 56 enters state 0 (Null).  Hold state: Idle
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: clearing, alive 1, hangupack
> 0
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:   == Primary D-Channel on
> span 7 up
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:     -- Channel 0/2, span 7
> got hangup, cause 27
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: T309 timed out waiting for
> data link re-establishment
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: q931.c:7750
> pri_internal_clear: Call 64 enters state 0 (Null).  Hold state: Idle
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: clearing, alive 1, hangupack
> 0
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:     -- Channel 0/3, span 7
> got hangup, cause 27
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: T309 timed out waiting for
> data link re-establishment
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: q931.c:7750
> pri_internal_clear: Call 58 enters state 0 (Null).  Hold state: Idle
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: clearing, alive 1, hangupack
> 0
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:     -- Channel 0/4, span 7
> got hangup, cause 27
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: T309 timed out waiting for
> data link re-establishment
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: q931.c:7750
> pri_internal_clear: Call 66 enters state 0 (Null).  Hold state: Idle
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: clearing, alive 1, hangupack
> 0
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c:     -- Channel 0/6, span 7
> got hangup, cause 27
> [Mar 18 17:04:15] VERBOSE[27353] pbx.c:   == Spawn extension (incoming-pri,
> sw-30-218543080, 11) exited non-zero on 'DAHDI/189-1'
> [Mar 18 17:04:15] VERBOSE[27353] chan_dahdi.c: q931_hangup: other hangup
> [Mar 18 17:04:15] VERBOSE[27354] app_mixmonitor.c:   == MixMonitor close
> filestream
> [Mar 18 17:04:15] VERBOSE[27353] chan_dahdi.c: NEW_HANGUP DEBUG: Calling
> q931_hangup, ourstate Null, peerstate Null, hold-state Idle
> [Mar 18 17:04:15] VERBOSE[27353] chan_dahdi.c: NEW_HANGUP DEBUG: Destroying
> the call, ourstate Null, peerstate Null, hold-state Idle
> [Mar 18 17:04:15] VERBOSE[27353] chan_dahdi.c:     -- Hungup
'DAHDI/189-1'
> [Mar 18 17:04:15] VERBOSE[27354] app_mixmonitor.c:   == Executing
> [/usr/local/bin/mixmon "1300465595.27894_withhold.gsm"
> "/var/log/asterisk/asterisk_rec/218543080/2011-03-18"]
> [Mar 18 17:04:15] VERBOSE[27279] pbx.c:   == Spawn extension (incoming-pri,
> sw-30-218543080, 11) exited non-zero on 'DAHDI/188-1'
> [Mar 18 17:04:15] VERBOSE[27279] chan_dahdi.c: q931_hangup: other hangup
> [Mar 18 17:04:15] VERBOSE[27279] chan_dahdi.c: NEW_HANGUP DEBUG: Calling
> q931_hangup, ourstate Null, peerstate Null, hold-state Idle
> [Mar 18 17:04:15] VERBOSE[27279] chan_dahdi.c: NEW_HANGUP DEBUG: Destroying
> the call, ourstate Null, peerstate Null, hold-state Idle
> [Mar 18 17:04:15] VERBOSE[27280] app_mixmonitor.c:   == MixMonitor close
> filestream
> [Mar 18 17:04:15] VERBOSE[27279] chan_dahdi.c:     -- Hungup
'DAHDI/188-1'
> [Mar 18 17:04:15] VERBOSE[27280] app_mixmonitor.c:   == Executing
> [/usr/local/bin/mixmon "1300465487.27876_219575683.gsm"
> "/var/log/asterisk/asterisk_rec/218543080/2011-03-18"]
> [Mar 18 17:04:15] VERBOSE[27954] pbx.c:   == Spawn extension (incoming-pri,
> sw-30-218543080, 11) exited non-zero on 'DAHDI/192-1'
> [Mar 18 17:04:15] VERBOSE[27955] app_mixmonitor.c:   == MixMonitor close
> filestream
> [Mar 18 17:04:15] VERBOSE[27954] chan_dahdi.c: q931_hangup: other hangup
> [Mar 18 17:04:15] VERBOSE[27954] chan_dahdi.c: NEW_HANGUP DEBUG: Calling
> q931_hangup, ourstate Null, peerstate Null, hold-state Idle
> [Mar 18 17:04:15] VERBOSE[27954] chan_dahdi.c: NEW_HANGUP DEBUG: Destroying
> the call, ourstate Null, peerstate Null, hold-state Idle
> [Mar 18 17:04:15] VERBOSE[27954] chan_dahdi.c:     -- Hungup
'DAHDI/192-1'
> [Mar 18 17:04:15] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:15] VERBOSE[27955] app_mixmonitor.c:   == Executing
> [/usr/local/bin/mixmon "1300467477.28066_229959499.gsm"
> "/var/log/asterisk/asterisk_rec/218543080/2011-03-18"]
> [Mar 18 17:04:15] VERBOSE[27487] pbx.c:   == Spawn extension (incoming-pri,
> sw-30-218543080, 11) exited non-zero on 'DAHDI/190-1'
> [Mar 18 17:04:15] VERBOSE[27487] chan_dahdi.c: q931_hangup: other hangup
> [Mar 18 17:04:15] VERBOSE[27488] app_mixmonitor.c:   == MixMonitor close
> filestream
> [Mar 18 17:04:15] VERBOSE[27487] chan_dahdi.c: NEW_HANGUP DEBUG: Calling
> q931_hangup, ourstate Null, peerstate Null, hold-state Idle
> [Mar 18 17:04:15] VERBOSE[27487] chan_dahdi.c: NEW_HANGUP DEBUG: Destroying
> the call, ourstate Null, peerstate Null, hold-state Idle
> [Mar 18 17:04:15] VERBOSE[27487] chan_dahdi.c:     -- Hungup
'DAHDI/190-1'
> [Mar 18 17:04:15] VERBOSE[27488] app_mixmonitor.c:   == Executing
> [/usr/local/bin/mixmon "1300466049.27932_263949634.gsm"
> "/var/log/asterisk/asterisk_rec/218543080/2011-03-18"]
> [Mar 18 17:04:16] VERBOSE[27280] app_mixmonitor.c:   == End MixMonitor
> Recording DAHDI/188-1
> [Mar 18 17:04:16] VERBOSE[27488] app_mixmonitor.c:   == End MixMonitor
> Recording DAHDI/190-1
> [Mar 18 17:04:16] VERBOSE[27354] app_mixmonitor.c:   == End MixMonitor
> Recording DAHDI/189-1
> [Mar 18 17:04:16] VERBOSE[27955] app_mixmonitor.c:   == End MixMonitor
> Recording DAHDI/192-1
> [Mar 18 17:04:16] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): T200
> expired N200 times sending SABME in state 5(Awaiting establishment)
> [Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: Changing from state
> 5(Awaiting establishment) to 4(TEI assigned)
> [Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
> Q931_DL_EVENT_DL_RELEASE_IND(3)
> [Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
> assigned) to 5(Awaiting establishment)
> [Mar 18 17:04:17] VERBOSE[19844] chan_dahdi.c:   == Primary D-Channel on
> span 7 down
> [Mar 18 17:04:17] WARNING[19844] chan_dahdi.c: No D-channels available!
>  Using Primary channel 202 as D-channel anyway!
> [Mar 18 17:04:18] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:19] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:20] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): T200
> expired N200 times sending SABME in state 5(Awaiting establishment)
> [Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: Changing from state
> 5(Awaiting establishment) to 4(TEI assigned)
> [Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
> Q931_DL_EVENT_DL_RELEASE_IND(3)
> [Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:21] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
> assigned) to 5(Awaiting establishment)
> [Mar 18 17:04:21] WARNING[19844] chan_dahdi.c: No D-channels available!
>  Using Primary channel 202 as D-channel anyway!
> [Mar 18 17:04:22] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:23] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:24] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: TEI=0 MDL-ERROR (G): T200
> expired N200 times sending SABME in state 5(Awaiting establishment)
> [Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: Changing from state
> 5(Awaiting establishment) to 4(TEI assigned)
> [Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: TEI=0 DL event:
> Q931_DL_EVENT_DL_RELEASE_IND(3)
> [Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:25] VERBOSE[19844] chan_dahdi.c: Changing from state 4(TEI
> assigned) to 5(Awaiting establishment)
> [Mar 18 17:04:25] WARNING[19844] chan_dahdi.c: No D-channels available!
>  Using Primary channel 202 as D-channel anyway!
> [Mar 18 17:04:26] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:27] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
> [Mar 18 17:04:28] VERBOSE[19844] chan_dahdi.c: TEI=0 Sending SABME
>
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110318/78365f38/attachment.htm>

Adrian Serafini

2011-Mar-18 18:17 UTC

head link

[asterisk-users] One PRI card with 2 (or more) Telcos

> Is there a problem having 2 telcos on the same PRI card?
I think you go with one master timer as the Telco.  Then the other spans 
are secondary, tertiary, quaternary timers.

Adrian

Andrew Latham

2011-Mar-18 18:21 UTC

head link

[asterisk-users] One PRI card with 2 (or more) Telcos

On Fri, Mar 18, 2011 at 3:17 PM, Adrian Serafini
<adrian-lists at wombit.com> wrote:>
>> Is there a problem having 2 telcos on the same PRI card?
>
> I think you go with one master timer as the Telco. ?Then the other spans
are
> secondary, tertiary, quaternary timers.
>
> Adrian

Adrian

This only works when all the providers are using a common clock like
some areas in the USA.  This is not the case all around the world.

-- 
~~~ Andrew "lathama" Latham lathama at gmail.com ~~~

Tiago Geada

2011-Mar-18 18:23 UTC

head link

[asterisk-users] One PRI card with 2 (or more) Telcos

Hi! I can try that tho. Where do I configure what timer to use??!

Thanks in advance.

On 18 March 2011 18:21, Andrew Latham <lathama at gmail.com> wrote:
> On Fri, Mar 18, 2011 at 3:17 PM, Adrian Serafini
> <adrian-lists at wombit.com> wrote:
> >
> >> Is there a problem having 2 telcos on the same PRI card?
> >
> > I think you go with one master timer as the Telco.  Then the other
spans
> are
> > secondary, tertiary, quaternary timers.
> >
> > Adrian
>
>
> Adrian
>
> This only works when all the providers are using a common clock like
> some areas in the USA.  This is not the case all around the world.
>
> --
> ~~~ Andrew "lathama" Latham lathama at gmail.com ~~~
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110318/d2620f2c/attachment-0001.htm>

Tiago Geada

2011-Mar-18 18:26 UTC

head link

[asterisk-users] One PRI card with 2 (or more) Telcos

OK I found it.

In /etc/dahdi/system.conf

I have for this span:


# Span 7: TE4/1/3 "T4XXP (PCI) Card 1 Span 3" HDB3/CCS/CRC4
span=7,7,0,ccs,hdb3,crc4
# termtype: te
bchan=187-201,203-217
dchan=202
echocanceller=mg2,187-201,203-217


should I use "span=7,*5*,0,ccs,hdb3,crc4" instead? (5 is the first
telco on
that card)

On 18 March 2011 18:23, Tiago Geada <tiago.geada at gmail.com> wrote:
> Hi! I can try that tho. Where do I configure what timer to use??!
>
> Thanks in advance.
>
> On 18 March 2011 18:21, Andrew Latham <lathama at gmail.com> wrote:
>
>> On Fri, Mar 18, 2011 at 3:17 PM, Adrian Serafini
>> <adrian-lists at wombit.com> wrote:
>> >
>> >> Is there a problem having 2 telcos on the same PRI card?
>> >
>> > I think you go with one master timer as the Telco.  Then the other
spans
>> are
>> > secondary, tertiary, quaternary timers.
>> >
>> > Adrian
>>
>>
>> Adrian
>>
>> This only works when all the providers are using a common clock like
>> some areas in the USA.  This is not the case all around the world.
>>
>> --
>> ~~~ Andrew "lathama" Latham lathama at gmail.com ~~~
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> New to Asterisk? Join us for a live introductory webinar every Thurs:
>>               http://www.asterisk.org/hello
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-users
>>
>
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110318/cbd026fe/attachment.htm>

Tiago Geada

2011-Mar-18 18:31 UTC

head link

[asterisk-users] One PRI card with 2 (or more) Telcos

Sorry to keep bugging, but after making changes to /etc/dahdi/system.conf,
do I need unload  res_timing_dahdi.so and chan_dahdi.so; and load them, or
can I just reload them??

Thanks in advance

On 18 March 2011 18:26, Tiago Geada <tiago.geada at gmail.com> wrote:
> OK I found it.
>
> In /etc/dahdi/system.conf
>
> I have for this span:
>
>
> # Span 7: TE4/1/3 "T4XXP (PCI) Card 1 Span 3" HDB3/CCS/CRC4
> span=7,7,0,ccs,hdb3,crc4
> # termtype: te
> bchan=187-201,203-217
> dchan=202
> echocanceller=mg2,187-201,203-217
>
>
> should I use "span=7,*5*,0,ccs,hdb3,crc4" instead? (5 is the
first telco
> on that card)
>
> On 18 March 2011 18:23, Tiago Geada <tiago.geada at gmail.com> wrote:
>
>> Hi! I can try that tho. Where do I configure what timer to use??!
>>
>> Thanks in advance.
>>
>> On 18 March 2011 18:21, Andrew Latham <lathama at gmail.com>
wrote:
>>
>>> On Fri, Mar 18, 2011 at 3:17 PM, Adrian Serafini
>>> <adrian-lists at wombit.com> wrote:
>>> >
>>> >> Is there a problem having 2 telcos on the same PRI card?
>>> >
>>> > I think you go with one master timer as the Telco.  Then the
other
>>> spans are
>>> > secondary, tertiary, quaternary timers.
>>> >
>>> > Adrian
>>>
>>>
>>> Adrian
>>>
>>> This only works when all the providers are using a common clock
like
>>> some areas in the USA.  This is not the case all around the world.
>>>
>>> --
>>> ~~~ Andrew "lathama" Latham lathama at gmail.com ~~~
>>>
>>> --
>>>
_____________________________________________________________________
>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com
--
>>> New to Asterisk? Join us for a live introductory webinar every
Thurs:
>>>               http://www.asterisk.org/hello
>>>
>>> asterisk-users mailing list
>>> To UNSUBSCRIBE or update options visit:
>>>   http://lists.digium.com/mailman/listinfo/asterisk-users
>>>
>>
>>
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110318/7c63c278/attachment.htm>

Danny Nicholas

2011-Mar-18 18:34 UTC

head link

[asterisk-users] One PRI card with 2 (or more) Telcos

Probably overkill, but "Every" time I make a change to dahdi, I do
this

Service asterisk stop

Service dadhi restart

Service asterisk start

  _____  

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Tiago Geada
Sent: Friday, March 18, 2011 1:31 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] One PRI card with 2 (or more) Telcos

Sorry to keep bugging, but after making changes to /etc/dahdi/system.conf,
do I need unload  res_timing_dahdi.so and chan_dahdi.so; and load them, or
can I just reload them??

Thanks in advance

On 18 March 2011 18:26, Tiago Geada <tiago.geada at gmail.com> wrote:

OK I found it. 

In /etc/dahdi/system.conf

I have for this span:

# Span 7: TE4/1/3 "T4XXP (PCI) Card 1 Span 3" HDB3/CCS/CRC4

span=7,7,0,ccs,hdb3,crc4

# termtype: te

bchan=187-201,203-217

dchan=202

echocanceller=mg2,187-201,203-217

should I use "span=7,5,0,ccs,hdb3,crc4" instead? (5 is the first telco
on
that card)

On 18 March 2011 18:23, Tiago Geada <tiago.geada at gmail.com> wrote:

Hi! I can try that tho. Where do I configure what timer to use??!

Thanks in advance.

On 18 March 2011 18:21, Andrew Latham <lathama at gmail.com> wrote:

On Fri, Mar 18, 2011 at 3:17 PM, Adrian Serafini
<adrian-lists at wombit.com> wrote:>
>> Is there a problem having 2 telcos on the same PRI card?
>
> I think you go with one master timer as the Telco.  Then the other spans
are> secondary, tertiary, quaternary timers.
>
> Adrian

Adrian

This only works when all the providers are using a common clock like
some areas in the USA.  This is not the case all around the world.

--
~~~ Andrew "lathama" Latham lathama at gmail.com ~~~

--
_____________________________________________________________________

-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
              http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20110318/51ff2863/attachment.htm>

Possibly Parallel Threads

Search for more possibly parallel threads

asterisk users - Mar 2011 - One PRI card with 2 (or more) Telcos

[asterisk-users] One PRI card with 2 (or more) Telcos

[asterisk-users] One PRI card with 2 (or more) Telcos

[asterisk-users] One PRI card with 2 (or more) Telcos

[asterisk-users] One PRI card with 2 (or more) Telcos

[asterisk-users] One PRI card with 2 (or more) Telcos

[asterisk-users] One PRI card with 2 (or more) Telcos

[asterisk-users] One PRI card with 2 (or more) Telcos

[asterisk-users] One PRI card with 2 (or more) Telcos

Possibly Parallel Threads