VoIP Mailing List Archives

[EWieling at nyigc.com]

We are seeing the message " PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP" on one of our Asterisk boxes on a PRI. A Google search turns up a number of hits for this error, but they are all for BRI not PRI.

I'm reasonably sure there are no recent updates or config changes.

Running Asterisk 1.4.37. We can update to 1.4.44 if it will help. At this time we cannot upgrade to anything later.

Does anyone know how I might troubleshoot this?


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

[webaccounts at jgoettg...]

MDL/TEI is pretty low level.

Which card are you using?

chan_dahdi.conf?

Card config?

PCAP trace? Q.931 and Q.921 messages are relatively easy to debug with wireshark.

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

[EWieling at nyigc.com]

I was not aware Wireshark worked on PRI spans. What interface should I tell it to watch? 8-|

Card is: wanpipe: AFT-A101-SH PCI T1/E1 card found (HDLC (DS) rev.37), cpu(s) 1

chan_dahdi.conf has a timestamp of Jun 25 of last year

# cat /etc/asterisk/chan_dahdi.conf
;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
;autogenrated on 2012-05-29
;Dahdi Channels Configurations
;For detailed Dahdi options, view /etc/asterisk/chan_dahdi.conf.bak

[trunkgroups]

[channels]
usecallerid=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
group=1
immediate=no
pridialplan=unknown
resetinterval=never

;Sangoma A101 port 1 [slot:2 bus:17 span:1] <wanpipe1>
switchtype=national
context=pbxmax
group=1
echocancel=yes
signalling=pri_cpe
channel =>1-23


PRI debug:

seidelnj*CLI> pri debug span 1
Enabled debugging on span 1
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of jg
Sent: Tuesday, February 18, 2014 3:12 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP

MDL/TEI is pretty low level.

Which card are you using?

chan_dahdi.conf?

Card config?

PCAP trace? Q.931 and Q.921 messages are relatively easy to debug with wireshark.

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

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

[lukasz.grzywanski at f...]

Hi,
http://wiki.sangoma.com/wanpipe-wireshark-pcap-pri-bri-wan-t1-e1-tracing





On 18 February 2014 21:34, Eric Wieling <EWieling@nyigc.com (EWieling@nyigc.com)> wrote:

[EWieling at nyigc.com]

In case anyone is confused about the message reported not showin up in pri debug. They show up in the Asterisk logs.
[2014-02-13 14:39:31] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:34] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:35] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:39] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:40] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:44] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:45] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:48] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:49] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:53] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:54] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:58] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:39:59] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:40:02] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:40:03] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!
[2014-02-13 14:40:06] WARNING[2932] chan_dahdi.c: PRI Error on span 1: Received MDL/TEI managemement message, but configured for mode other than PTMP!


-----Original Message-----
From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Eric Wieling
Sent: Tuesday, February 18, 2014 3:34 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP

I was not aware Wireshark worked on PRI spans. What interface should I tell it to watch? 8-|

Card is: wanpipe: AFT-A101-SH PCI T1/E1 card found (HDLC (DS) rev.37), cpu(s) 1

chan_dahdi.conf has a timestamp of Jun 25 of last year

# cat /etc/asterisk/chan_dahdi.conf
;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit ;autogenrated on 2012-05-29 ;Dahdi Channels Configurations ;For detailed Dahdi options, view /etc/asterisk/chan_dahdi.conf.bak

[trunkgroups]

[channels]
usecallerid=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
group=1
immediate=no
pridialplan=unknown
resetinterval=never

;Sangoma A101 port 1 [slot:2 bus:17 span:1] <wanpipe1> switchtype=national context=pbxmax
group=1
echocancel=yes
signalling=pri_cpe
channel =>1-23


PRI debug:

seidelnj*CLI> pri debug span 1
Enabled debugging on span 1
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of jg
Sent: Tuesday, February 18, 2014 3:12 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP

MDL/TEI is pretty low level.

Which card are you using?

chan_dahdi.conf?

Card config?

PCAP trace? Q.931 and Q.921 messages are relatively easy to debug with wireshark.

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

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

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

[EWieling at nyigc.com]

Nifty! I never knew that.

Here is a pcap:

http://help.nyigc.net/tmp/isdn.pcap


-----Original Message-----
From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Lukasz Grzywanski
Sent: Tuesday, February 18, 2014 3:37 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP

Hi,

http://wiki.sangoma.com/wanpipe-wireshark-pcap-pri-bri-wan-t1-e1-tracing



On 18 February 2014 21:34, Eric Wieling <EWieling@nyigc.com> wrote:


I was not aware Wireshark worked on PRI spans. What interface should I tell it to watch? 8-|

Card is: wanpipe: AFT-A101-SH PCI T1/E1 card found (HDLC (DS) rev.37), cpu(s) 1

chan_dahdi.conf has a timestamp of Jun 25 of last year

# cat /etc/asterisk/chan_dahdi.conf
;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
;autogenrated on 2012-05-29
;Dahdi Channels Configurations
;For detailed Dahdi options, view /etc/asterisk/chan_dahdi.conf.bak

[trunkgroups]

[channels]
usecallerid=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
group=1
immediate=no
pridialplan=unknown
resetinterval=never

;Sangoma A101 port 1 [slot:2 bus:17 span:1] <wanpipe1>
switchtype=national
context=pbxmax
group=1
echocancel=yes
signalling=pri_cpe
channel =>1-23


PRI debug:

seidelnj*CLI> pri debug span 1
Enabled debugging on span 1
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)
TEI=0 Got SABME from network peer.
TEI=0 Sending UA
TEI=0 MDL-ERROR (F): SABME in state 7(Multi-frame established)


-----Original Message-----
From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of jg
Sent: Tuesday, February 18, 2014 3:12 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP

MDL/TEI is pretty low level.

Which card are you using?

chan_dahdi.conf?

Card config?

PCAP trace? Q.931 and Q.921 messages are relatively easy to debug with wireshark.

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

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





--

Pozdrawiam,

Łukasz Grzywański
Senior Voice Engineer

Fast White Cat S.A.
ul. Św.Mikołaja 8-11, 50-125 Wrocław, Polska tel. +48 717226000, fax +48 717226099 mob. +48 517255333, e-mail: lukasz.grzywanski@fastwhitecat.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

[webaccounts at jgoettg...]

Eric,

since you seem to have a Sangoma card, you should contact Sangoma's excellent technical support.
I'll have a look at your pcap trace tomorrow. You can also download the relevant Q.931 and Q.921
docs from ITU's web server.

Sangoma's wanpipe drivers allow you to configure a few hardware things. Can you post the config
of one of your spans?

Besides this, what is your libpri version? Maybe this relates to your problem
(https://issues.asterisk.org/jira/browse/PRI-152?page=com.atlassian.streams.streams-jira-plugin:activity-stream-issue-tab)

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

[EWieling at nyigc.com]

My recent experiences with Sangoma tech support have been less than good. I admit the issue was rather wieid. We had an issue about a year ago where Sangoma PCI cards would not work in the servers we were purchasing unless you used a PCI/PCI-X converter/riser card. Everything would load but card would not work. On analog cards, the ports stayed red even after pluggin lines, on PRIs the span would appear to come up, but no interrupts were seen on the card. After 2 weeks of Sangoma blaming the circuit I finally gave up and ordered riser cards for all our remaining PCI Sangoma cards. Once all the older PCI cards were used from stock we started using PCI-X cards and didn't have the problem again.

We will be rebooting the server after hours, if that doesn't fix it, I'll update to a recent DAHDI, latest libpri, latest wanpipe, and latest Asterisk 1.4.x and see if the issue continues. I suspect a change on the telco side, but I can't prove it.

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of jg
Sent: Tuesday, February 18, 2014 4:55 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP

Eric,

since you seem to have a Sangoma card, you should contact Sangoma's excellent technical support.
I'll have a look at your pcap trace tomorrow. You can also download the relevant Q.931 and Q.921 docs from ITU's web server.

Sangoma's wanpipe drivers allow you to configure a few hardware things. Can you post the config of one of your spans?

Besides this, what is your libpri version? Maybe this relates to your problem
(https://issues.asterisk.org/jira/browse/PRI-152?page=com.atlassian.streams.streams-jira-plugin:activity-stream-issue-tab)

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

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

[mcgrathr at mail2web.com]

It seems a layer 2 problem, should check about references point (network or terminal equipment), it assume your Asterisk box is connected to ISDN PSTN provided, just in case check at you side if all related configuration files are configured as signalling=pri_cpe (Card config, wan_cfg, chan_dahdi.conf), PSTN side if network configuration or in service mode, should both side work and debug in the same time.

Mc GRATH Ricardo
E-Mail mcgrathr@mail2web.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

[webaccounts at jgoettg...]

Eric!

The pcap trace seems to contain only idle data, and there is nothing unusual.

As far as I know, PRI always uses the static TEI value of 0, as there is only a single
"terminal equipment (TE). The TEI assignment procedure is only relevant if there is a BRI
connection on a so called "S0 bus" and the TE operates in point-to-multipoint mode. Then the
automatically assigned TEI is within the range 64 to 126. Sangoma ISDN products using
DAHDI/libpri do not have any problem with this in any mode.

There are always spurious MDL (related to supervisory frames, or so) messages, but they have no
impact on actual calls.

If there many calls on ISDN lines and you need to restart Asterisk/DAHDI/Wanpipe, then it is
likely that the system is in an inconsistent state. Some phones ring, but cannot be answered, or
answered and the other side cannot hear the other side, and stuff like that. I don't see right
now how this relates to your problem, but you could try to capture the SETUP (followed by CALL
PROCEEDING, ALERTING, CONNECT, STATUS, ...) messages from in- and outbound calls and log what
happens.

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

[EWieling at nyigc.com]

A reboot of the system after hours appears to have solved the issue.


-----Original Message-----
From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of jg
Sent: Wednesday, February 19, 2014 11:15 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] PRI Error on span 1: Received MDL/TEI management message, but configured for mode other than PTMP

Eric!

The pcap trace seems to contain only idle data, and there is nothing unusual.

As far as I know, PRI always uses the static TEI value of 0, as there is only a single "terminal equipment (TE). The TEI assignment procedure is only relevant if there is a BRI connection on a so called "S0 bus" and the TE operates in point-to-multipoint mode. Then the automatically assigned TEI is within the range 64 to 126. Sangoma ISDN products using DAHDI/libpri do not have any problem with this in any mode.

There are always spurious MDL (related to supervisory frames, or so) messages, but they have no impact on actual calls.

If there many calls on ISDN lines and you need to restart Asterisk/DAHDI/Wanpipe, then it is likely that the system is in an inconsistent state. Some phones ring, but cannot be answered, or answered and the other side cannot hear the other side, and stuff like that. I don't see right now how this relates to your problem, but you could try to capture the SETUP (followed by CALL PROCEEDING, ALERTING, CONNECT, STATUS, ...) messages from in- and outbound calls and log what happens.

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

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