Summary: | ASTERISK-02080: E1 stopped working in recent CVS. | ||
Reporter: | oliver (oliver) | Labels: | |
Date Opened: | 2004-07-22 04:05:19 | Date Closed: | 2004-09-25 02:37:47 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Since a recent update of Zaptel from CVS, the E1 connected to that box through a TE410P has stopped working. The D-channel simply no longer comes up. "pri intense debug span 1" shows one of these about every second when it goes wrong: > Unnumbered frame: > SAPI: 00 C/R: 0 EA: 0bug span > TEI: 000 EA: 1 > M3: 3 P/F: 1 M2: 3 11: 3 [ SABME (set asynchronous balanced mode extended) ] > 0 bytes of data Reverting to the Zaptel-version dated 07/14/04 from CVS fixes this problem. ****** ADDITIONAL INFORMATION ****** Dual Xeon 2.4GHz. Asterisk CVS-HEAD-07/22/04-10:23:38. Relevant parts of config-files: /etc/zaptel.conf: span=1,1,0,ccs,hdb3 bchan=1-15 dchan=16 bchan=17-31 /etc/asterisk/zapata.conf: switchtype=euroisdn signalling=pri_cpe context=<context> group=1 switchtype=euroisdn signalling=pri_cpe relaxdtmf=no immediate=no overlapdial=yes channel => 1-15,17-31 | ||
Comments: | By: adomjan (adomjan) 2004-07-22 18:36:58 I tried upgrade my system from e100p to te405p, and failed with the same problem. cvs: 07/21/04, so I changed back to e100p. By: Mark Spencer (markster) 2004-07-22 19:45:54 Can you identify specifically which version introduced the problem? By: Mark Spencer (markster) 2004-07-22 19:48:47 Nevermind, found it. It's fixed in CVS, if not, just reopen. |