Hello List,

 We scheduled an mISDN + Asterisk upgrade for this weekend.
 Unfortunatelly, not all things went well and, as the subject says.
 We appreciate any help, pointers, feedback and experiences !

 :-)

 Original setup:

   mISDN 1.0.4 + mISDNuser 1.0.3
   zaptel 1.2.12
   asterisk 1.2.14 + bundled chan_misdn

 Target setup:

   mISDN 1.1.1 + mISDNuser 1.1.1
   zaptel 1.2.16
   asterisk 1.2.17 + bundled chan_misdn

 The procedure we followed was:

   1. Stop asterisk
   2. remove zaptel modules with rmmod (zaptel + wctdm)
   3. misdn-init stop to remove the mISDN modules
   4. Remove all mISDN files + zaptel files while saving /etc/misdn-init.conf
       and /etc/zaptel.conf
   5. Build and install new mISDN release
   6. Build and install new zaptel release
   7. Build and install new asterisk release
   8. misdn-init scan ok
   9. misdn-init config ok (generates very similar config file)
   10. misdn-init start ok - kernel buffer messages look fine
   11. ztcfg ok
   12. loaded zaptel drivers
   13. asterisk startup ok

 Result:

   Dialing in works ok for our 10 DDIs
   Dialing out always gives us the busy tone.
   No other changes have been made to misdn.conf nor to extensions.conf

   We rebooted the system so as to be 100% sure there was no data in
   kernel from the previous versions.

 Our fallback:

   1. Stopped everything, removed all mISDN-1.1.1 files
   2. Installed mISDN 1.0.4 + mISDNuser 1.0.3 again
   3. Rebuilt + installed chan_misn bundled from asterisk 1.2.17
   4. Kept zaptel 1.2.16 and asterisk 1.2.17

 Our reasoning to date:

   We certainly did something wrong, but we can't seem to find it !
   For now, the issue seems to be around the mISDN driver layer upgrade
   because the chan_misdn upgrade (bundled with asterisk) seems to
   have no negative effect.

   We attach misdn.log with debug=3 for the failing dial out with 1.1.1 and
   the same log for a successfull dial out with 1.0.4 / 1.0.3.

   Can anyone spot our errors ?

   BTW, two last questions:

   1. How can we tell which chan_misdn version is bundled with each
       asterisk version ?

   2. Is this mailing list adequate for this kind of issues or should we use
       isdn4linux ? Some other ?

 Thanks a lot in advance.
 Kind regards,
--
 Ex Vito

Attachment: misdn.111.111
Description: Binary data

Attachment: misdn.104.103
Description: Binary data

_______________________________________________
Misdn-asterisk mailing list
[email protected]
http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk

Reply via email to