[asterisk-users] MDL-ERROR

2013-09-05 Thread jg
I have 2 ISDN BRI boxes, each with 4 spans, where the first one is configured as CPE, the second 
one as NET(so I don't need real lines for developing and testing).


Once in a while I do see the following libpri error messages simultaneously on 
both boxes:

PRI Span: 1 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)
...
PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 
7(Multi-frame established)

It does not seem to be a severe error, because everything seems to work. I have not yet figured 
out how to produce these error messages reliably. They seem to appear after booting both 
machines before any calls have been made.


Does anybody know what to do with these messages?

The BRI cards are 100% ok and I have never seen these messages when connected 
to a public circuit.

jg

--
_
-- 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


Re: [asterisk-users] MDL-ERROR

2013-09-05 Thread Richard Mudgett
On Thu, Sep 5, 2013 at 1:02 PM, jg webaccou...@jgoettgens.de wrote:

 I have 2 ISDN BRI boxes, each with 4 spans, where the first one is
 configured as CPE, the second one as NET(so I don't need real lines for
 developing and testing).

 Once in a while I do see the following libpri error messages
 simultaneously on both boxes:

 PRI Span: 1 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 ...
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)

 It does not seem to be a severe error, because everything seems to work. I
 have not yet figured out how to produce these error messages reliably. They
 seem to appear after booting both machines before any calls have been made.

 Does anybody know what to do with these messages?


Q.921 just says to log the condition and carry on as if it did not happen.
It does not say what to do
about it.  The condition is likely to happen when the Q.921 peers are out
of sync with each other.  When
you reboot your machines, they will be out of sync with each other for
awhile.  I cannot think of a
particular sequence of events off-hand where it would happen though.

Richard
--
_
-- 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

Re: [asterisk-users] MDL-ERROR

2013-09-05 Thread Mikhail Lischuk
 

Mitul Limbani писал 05.09.2013 21:43: 

 Something very
similar happened on our boxes and we did nothing special apart from
changing DAHDI and Asterisk versions to higher stable (2.6.1 n 1.8.14
respectively) and it went off. 
 
 Don't really know exactly why it
happens, it would be worthwhile to investigate if you see it again on
CLI or logs. 
 
 Mitul 
 
 On Friday, September 6, 2013, Richard
Mudgett wrote:
 
 On Thu, Sep 5, 2013 at 1:02 PM, jg
webaccou...@jgoettgens.de wrote:
 
 I have 2 ISDN BRI boxes, each
with 4 spans, where the first one is configured as CPE, the second one
as NET(so I don't need real lines for developing and testing).
 

Once in a while I do see the following libpri error messages
simultaneously on both boxes:
 
 PRI Span: 1 TEI=0 MDL-ERROR (A):
Got supervisory frame with F=1 in state 7(Multi-frame established)

PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got
supervisory frame with F=1 in state 7(Multi-frame established)
 PRI
Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got
supervisory frame with F=1 in state 7(Multi-frame established)
 PRI
Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got
supervisory frame with F=1 in state 7(Multi-frame established)
 PRI
Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got
supervisory frame with F=1 in state 7(Multi-frame established)
 PRI
Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got
supervisory frame with F=1 in state 7(Multi-frame established)
 PRI
Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
7(Multi-frame established)
 ...
 PRI Span: 4 TEI=0 MDL-ERROR (A):
Got supervisory frame with F=1 in state 7(Multi-frame established)


 It does not seem to be a severe error, because everything seems to
work. I have not yet figured out how to produce these error messages
reliably. They seem to appear after booting both machines before any
calls have been made.
 
 Does anybody know what to do with these
messages?
 
 Q.921 just says to log the condition and carry on as if
it did not happen. It does not say what to do
 about it. The condition
is likely to happen when the Q.921 peers are out of sync with each
other. When
 you reboot your machines, they will be out of sync with
each other for awhile. I cannot think of a
 particular sequence of
events off-hand where it would happen though.
 
 Richard
 
 -- 


 Regards,
 Mitul Limbani,
 Chief Architech  Founder,
 Enterux
Solutions Pvt. Ltd.
 110 Reena Complex, Opp. Nathani Steel, 

Vidyavihar (W), Mumbai - 400 086. India
 http://www.enterux.com/ [4]

http://www.entvoice.com/ [5]
 email: mi...@enterux.in
 DID:
+91-22-71967196
 Cell: +91-9820332422
 
 --

_

-- Bandwidth and Colocation Provided by http://www.api-digital.com [1]
--
 New to Asterisk? Join us for a live introductory webinar every
Thurs:
 http://www.asterisk.org/hello [2]
 
 asterisk-users mailing
list
 To UNSUBSCRIBE or update options visit:

http://lists.digium.com/mailman/listinfo/asterisk-users [3]

-- 
With
Best Regards
Mikhail Lischuk

+380681244933

+380504182274




Links:
--
[1] http://www.api-digital.com
[2]
http://www.asterisk.org/hello
[3]
http://lists.digium.com/mailman/listinfo/asterisk-users
[4]
http://www.enterux.com/
[5] http://www.entvoice.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

Re: [asterisk-users] MDL-ERROR

2013-09-05 Thread jg



Q.921 just says to log the condition and carry on as if it did not happen.

I guess you mean: carry on if it happened (and don't care any more).

Sorry, English is not my mother tongue. I didn't see the 'not'.


--
_
-- 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


Re: [asterisk-users] MDL-ERROR

2013-09-05 Thread Mitul Limbani
Something very similar happened on our boxes and we did nothing special
apart from changing DAHDI and Asterisk versions to higher stable (2.6.1 n
1.8.14 respectively) and it went off.

Don't really know exactly why it happens, it would be worthwhile to
investigate if you see it again on CLI or logs.

Mitul

On Friday, September 6, 2013, Richard Mudgett wrote:




 On Thu, Sep 5, 2013 at 1:02 PM, jg 
 webaccou...@jgoettgens.dejavascript:_e({}, 'cvml', 
 'webaccou...@jgoettgens.de');
  wrote:

 I have 2 ISDN BRI boxes, each with 4 spans, where the first one is
 configured as CPE, the second one as NET(so I don't need real lines for
 developing and testing).

 Once in a while I do see the following libpri error messages
 simultaneously on both boxes:

 PRI Span: 1 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 2 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)
 ...
 PRI Span: 4 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state
 7(Multi-frame established)

 It does not seem to be a severe error, because everything seems to work.
 I have not yet figured out how to produce these error messages reliably.
 They seem to appear after booting both machines before any calls have been
 made.

 Does anybody know what to do with these messages?


 Q.921 just says to log the condition and carry on as if it did not
 happen.  It does not say what to do
 about it.  The condition is likely to happen when the Q.921 peers are out
 of sync with each other.  When
 you reboot your machines, they will be out of sync with each other for
 awhile.  I cannot think of a
 particular sequence of events off-hand where it would happen though.

 Richard



-- 
Regards,
Mitul Limbani,
Chief Architech  Founder,
Enterux Solutions Pvt. Ltd.
110 Reena Complex, Opp. Nathani Steel,
Vidyavihar (W), Mumbai - 400 086. India
http://www.enterux.com/
http://www.entvoice.com/
email: mi...@enterux.in
DID: +91-22-71967196
Cell: +91-9820332422
--
_
-- 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

Re: [asterisk-users] MDL-ERROR

2013-09-05 Thread jg



Q.921 just says to log the condition and carry on as if it did not happen.

I guess you mean: carry on if it happened (and don't care any more).


It does not say what to do
about it.
It seems that making some calls makes these error messages go away. I am going to write a test 
script that monitors the log file for the message and triggers a call if one occurs. Then I'll 
see whether my hypothesis is correct.



The condition is likely to happen when the Q.921 peers are out of sync with 
each other.  When
you reboot your machines, they will be out of sync with each other for awhile.
It doesn't happen all the time, though. I have skimmed, but not studied, the Q.921 ITU specs 
already, and for synchronization it may be necessary that libpri is active (essentially getting 
* to run ASAP after starting the machine) and that just starting the driver (wanrouter in my 
case) is not sufficient to sync the cards. I have to test this, but the idea is that letting the 
cards communicate without some higher level support from libpri may be responsible for the error 
condition.



I cannot think of a
particular sequence of events off-hand where it would happen though.

I'll keep watching for whatever might trigger the error condition.

jg


--
_
-- 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