[...] To clear any possibility of having missed something in
the upgrade procedure, we'll set up a test system this next
weekend from scratch: base os + misdn + zaptel
+ asterisk.
We'll update the list on our results.
FYI, we did prepare a test system from scratch:
- Ubuntu server 6.06 LTS with kernel 2.6.15-26-server
- mISDN 1.1.1 + mISDNuser 1.1.1
- zaptel 1.2.16
- Asterisk 1.2.17
Both dial out and dial in tested and operational. Conclusion:
a) either we did something wrong in our upgrade procedure
b) or we had some transient failures in the telco by the time of the upgrade
...of course, we're considering a) as the most probable since we rolled back
mISDN versions and the system operated correctly again !
Our procedure was:
1. stop asterisk
2. misdn-init stop
3. remove mISDN files
4. remove mISDNuser files
5. build + install new releases of mISDN & mISDNuser
6. misdn-init config
7. tweak /etc/misdn-init.conf
8. misdn-init start
9. check modules loaded ok
10. reboot system (start from a fresh kernel)
11. rebuild chan_misdn bundled with asterisk 1.2.17
(it seems to be needed otherwise the data-xfer from/to kernel
is garbled -- in particular we had funny results in the oad: dad:
fields under misdn.log)
12. start asterisk
Our current guesses:
a) we did not clean old files 100% correctly in steps 3. and 4.
(is there any 100% safe way of knowing which these are ? we've
been installing
on a test system and identifying created files after mISDN installation)
b) Maybe we need a reboot after step 4 so that we build in a 100% clean
memory kernel ? (then again, why ?)
c) Maybe we need to better check for the mISDN header files (since
under Ubuntu we
have to "make force" ?...)
Any recommendations, best practises, hints ?
Thanks in advance and kind regards,
--
Ex Vito
_______________________________________________
Misdn-asterisk mailing list
[email protected]
http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk
