No subject


Fri Sep 2 03:59:05 CDT 2011


{quote}
; BRI PTMP layer 1 presence.
; You should normally not need to set this option.
; You may need to set this option if your telco brings layer 1 down when
; the line is idle.
; required:      Layer 1 presence required for outgoing calls. (default)
; ignore:        Ignore alarms from DAHDI about this span.
;                (Layer 1 and 2 will be brought back up for an outgoing call.)
;                NOTE:  You will not be able to detect physical line problems
;                until an outgoing call is attempted and fails.
;
;layer1_presence=ignore

; BRI PTMP layer 2 persistence.
; You should normally not need to set this option.
; You may need to set this option if your telco brings layer 1 down when
; the line is idle.
; <blank>:       Use libpri default.
; keep_up:       Bring layer 2 back up if peer takes it down.
; leave_down:    Leave layer 2 down if peer takes it down. (Libpri default)
;                (Layer 2 will be brought back up for an outgoing call.)
;
;layer2_persistence=leave_down
{quote}


This is not a bug and I am closing the issue.
                
> Pri state stays up when cable is unplugged (DAHDI ISDN cologne chipset)
> -----------------------------------------------------------------------
>
>                 Key: PRI-156
>                 URL: https://issues.asterisk.org/jira/browse/PRI-156
>             Project: LibPRI
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 1.4.13
>         Environment: Linux asterisk-backup 2.6.32-5-686-bigmem #1 SMP Mon Feb 25 01:53:47 UTC 2013 i686 GNU/Linux
> /etc/debian_version 6.0.7
> Asterisk 1.8.15.0
> DAHDI Tools Version - 2.6.1
> dahdi.ko version:d965594
>            Reporter: Stijn Van Campenhout
>            Assignee: Richard Mudgett
>            Severity: Minor
>
> Whenever an isdn line is disconnected (cable unplugged) from my ISDN card (cologne chipset), pri debug shows it state changed to REMOVE, but `pri show spans` keeps displaying it as Up,Active
> `pri set debug on span 1` output when unplugged:
> asterisk-backup*CLI> pri set debug on span 1
> Enabled debugging on span 1
> PRI Span: 1 TEI=72 MDL-ERROR (I): T200 expired N200 times sending RR/RNR in state 8(Timer recovery)
> PRI Span: 1 TEI=72 Sending SABME
> PRI Span: 1 Changing from state 8(Timer recovery) to 5(Awaiting establishment)
> PRI Span: 1 TEI=72 Sending SABME
> PRI Span: 1 TEI=72 Sending SABME
> PRI Span: 1 TEI=72 Sending SABME
> PRI Span: 1 TEI=72 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
> PRI Span: 1 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
> PRI Span: 1 TEI=72 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
> PRI Span: 1 MDL-REMOVE: Removing TEI 72
> PRI Span: 1 Changing from state 4(TEI assigned) to 1(TEI unassigned)
> PRI Span: 1 TEI=72 DL event: Q931_DL_EVENT_TEI_REMOVAL(5)
> asterisk-backup*CLI> pri show spans
> PRI span 1/0: Up, Active
> PRI span 2/0: Down, Active
> PRI span 3/0: Down, Active
> When I reload DAHDI, then it gets marked as down:
> asterisk-backup*CLI> dahdi restart
>  Destroying channels and reloading DAHDI configuration.
>        > Initial softhangup of all DAHDI channels complete.
>        > Final softhangup of all DAHDI channels complete.
>     -- Unregistered channel -2
>     -- Unregistered channel 1
>     -- Unregistered channel 2
>     -- Unregistered channel 4
>     -- Unregistered channel 5
>     -- Unregistered channel 7
>     -- Unregistered channel 8
>   == Parsing '/etc/asterisk/chan_dahdi.conf':   == Found
>   == Parsing '/etc/asterisk/dahdi-channels.conf':   == Found
> [2013-03-08 16:57:49] WARNING[5838]: config.c:1238 process_text_line: Unknown directive '#group=1' at line 26 of /etc/asterisk/chan_dahdi.conf
>     -- Reconfigured channel 1, ISDN BRI Point to MultiPoint signalling
>     -- Reconfigured channel 2, ISDN BRI Point to MultiPoint signalling
>     -- Reconfigured channel 4, ISDN BRI Point to MultiPoint signalling
>     -- Reconfigured channel 5, ISDN BRI Point to MultiPoint signalling
>     -- Reconfigured channel 7, ISDN BRI Point to MultiPoint signalling
>     -- Reconfigured channel 8, ISDN BRI Point to MultiPoint signalling
>     -- Automatically generated pseudo channel
>   == Starting D-Channel on span 1
>   == Starting D-Channel on span 2
>   == Starting D-Channel on span 3
> asterisk-backup*CLI> pri show spans
> PRI span 1/0: Down, Active
> PRI span 2/0: Down, Active
> PRI span 3/0: Down, Active
> But when I plug the cable back in, its correctly marked as up:
> asterisk-backup*CLI> pri set debug  on span 1
> Enabled debugging on span 1
> PRI Span: 1 Sending TEI management message 1(TEI Identity Request), TEI=127
> PRI Span: 1 Received MDL message
> PRI Span: 1 TEI assignment received for another Ri 15c8 (ours is 8663)
> PRI Span: 1 Received MDL message
> PRI Span: 1 TEI assignment received for another Ri 785a (ours is 8663)
> PRI Span: 1 Received MDL message
> PRI Span: 1 Got assigned TEI 75
> PRI Span: 1 Changing from state 2(Assign awaiting TEI) to 4(TEI assigned)
> PRI Span: 1 TEI=75 Sending SABME
> PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
> Span 1: Processing event PRI_EVENT_DCHAN_UP
>   == Primary D-Channel on span 1 up
> PRI Span: 1 TEI=75 Got UA
> PRI Span: 1 Changing from state 5(Awaiting establishment) to 7(Multi-frame established)
> PRI Span: 1 TEI=75 DL event: Q931_DL_EVENT_DL_ESTABLISH_CONFIRM(2)
> asterisk-backup*CLI> pri show spans
> PRI span 1/0: Up, Active
> PRI span 2/0: Down, Active
> PRI span 3/0: Down, Active

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list