[asterisk-bugs] [JIRA] (PRI-165) Need to respond to the MDL messages in point-to-point mode.

[Denis Alberto Martinez (JIRA)]

    [ https://issues.asterisk.org/jira/browse/PRI-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217559#comment-217559 ] 

Denis Alberto Martinez commented on PRI-165:
--------------------------------------------

Customer feedback

I made other tests today.

The behavior of the system *with* the patch was OK during 24 hours. No difficulty were detected by the customer. I do not see problems in  the log either.

_*Test A :*_
See attached file :
20140424-asterisk-l1ignore-l2leave_down-withoutpatch.log.gz
20140424-asterisk-dahdishowstatus-withoutpatch.log.gz (result of dahdi 
show status every minute)

I re-installed the non-patched libpri without changing the configuration  and made some tests. It reveals that without the patch, the system does not behave correctly.  Particularly the second span never went up again. All incoming calls sent by the operator on this span failed. chan_dahdi didn't try to UP the span when you issue an outgoing call on 
this span 

Note :
- incoming calls were sent at 11:06:05, 11:06:20, 11:07:20, 11:07:46, 
11:08:10
- outgoing calls were issued at 11:14:51 (ok span 1), 11:15:40 (ok span 3)


_*Test B :*_
See attached file :
20140424-asterisk-l1ignore-l2leave_down-withpatch.log.gz
20140424-asterisk-dahdishowstatus-withpatch.log.gz (result of dahdi show 
status every minute)

Since it didn't work, I re-installed the patched libpri and restarted 
the services.
With only a dahdi + asterisk restart, the service never came back.
No incoming calls on span 2, span 2 stays RED.

See log from 11:17:00 to 11:40:00.

I then asked the customer to unplug the BRI lines at the operator side 
and to plug them back.
See log :
- 11:42:44 - span 1 replugged
- 11:47:20 - span 2 replugged (was incorrectly plugged at 11:45:11)
- 11:48:20 - span 3 replugged

After having unplug and replug the SPAN, all SPAN were OK but no  incoming and no outgoing calls were possible.
See log from 11:48:00 -> 11:54:00.

I then restarted asterisk : incoming calls were now possible (first restart at 11:54:14 - with option pritimer = n200,10 but 
probably without effect - and second restart at 11:55:04 without the  pritimer option).

_*My 'conclusions' are :*_
The patch seems to make the system more stable when the system is working. But, if the system becomes unstable, the patch doesn't permit to recover  normal operation (which is coherent with what you hint that is that  there is a second problem with L1 establishment/negotiation). 

Then I'm also still puzzled with chan_dahdi/dahdi behavior in l1ignore 
and l2leave_down mode since :
- L2 is always up
- chan_dahdi doesn't seem to UP L1/L2 when you try to issue an outgoing 
call on a RED SPAN.


> Need to respond to the MDL messages in point-to-point mode. 
> ------------------------------------------------------------
>
>                 Key: PRI-165
>                 URL: https://issues.asterisk.org/jira/browse/PRI-165
>             Project: LibPRI
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 1.4.13
>         Environment: BRI
>            Reporter: Denis Alberto Martinez
>            Assignee: Richard Mudgett
>         Attachments: BRI.zip, jira_pri_165_ptp_respond_tei_check.patch
>
>
> {quote}
> (03/12/2014 05:16:32 PM) Richard Mudgett: I think most of the problems will go away if libpri is modified to respond to the MDL messages in point-to-point mode.  Modifying q921.c in libpri shouldn't be too difficult to do this.  A JIRA issue just needs to be created and scheduled.
> (03/12/2014 05:17:47 PM) Richard Mudgett: The other issue that would need to be looked into is the layer 1 start problem they also saw.  That would need to be fixed in DAHDI.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.2#6252)