<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Thanks Tzafrir, kinda weird results though. <BR>
cat /sys/module/zaptel/version did report 1.4.8 was installed once I issued the ./live_zap unload, load sequence. I was able to make a call out through the FXO fine. Not being certain that everything was loaded I decided to issue a "zap restart" command from the CLI. This totally shut down the trunk. When I issued a "Zap show status" command I noticed that ZTDummy/1 was no longer present. If I am interpreting the status returned text correctly, ZTDummy is the source of my clocking so this scenario of totally loosing the trunk makes sense. Why would it show ZTDummy (RTC) when I have an FXO card?<BR>
<BR>
However I'm not sure if I'm any further ahead. Potentially I think that I could simply copy the chan_zap.so module to my modules folder, restart asterisk and all would be fine. This seems too easy. Would you say that the module being loaded is an indication that everything was working fine? <BR>
<BR>
This is getting kinda complicated for me to ascertain a good method for troubleshooting what is breaking, and whether copying the module over instead of using make install is appropriate. Any suggestions?<BR>
<BR>
Thanks.. Syd<BR>
<BR><BR>> Date: Fri, 18 Jan 2008 14:53:01 +0200<BR>> From: tzafrir.cohen@xorcom.com<BR>> To: asterisk-dev@lists.digium.com<BR>> Subject: Re: [asterisk-dev] Zaptel-1.4.8; Zap trunk reverts to dialtone instead of processing call<BR>> <BR>> On Thu, Jan 17, 2008 at 08:41:23PM -0500, syd wonder wrote:<BR>> > <BR>> > Thanks for the advice. I was able to partially follow it. Here are my results.. Does this help any?<BR>> > <BR>> > uname -r results in 2.6.18-8.1.8.e15-i686<BR>> > using X100P<BR>> > <BR>> > Tried ./live_zap, unload, load - but couldn't tell whether the 1.4.7.1 <BR>> > zap was replaced with 1.4.8; and problem didn't show up.<BR>> ><BR>> > Reviewed your webpage but still wasn't sure hot to tell if I was using <BR>> > 1.4.8 ver. Don't think there was a need to adjust modules since <BR>> > live_zap reported the correct card.<BR>> <BR>> To check what version of Zaptel is actually loaded: <BR>> <BR>> cat /sys/module/zaptel/version<BR>> <BR>> (Works as of around 2.6.10)<BR>> <BR>> -- <BR>> Tzafrir Cohen<BR>> icq#16849755 jabber:tzafrir.cohen@xorcom.com<BR>> +972-50-7952406 mailto:tzafrir.cohen@xorcom.com<BR>> http://www.xorcom.com iax:guest@local.xorcom.com/tzafrir<BR>> <BR>> _______________________________________________<BR>> --Bandwidth and Colocation Provided by http://www.api-digital.com--<BR>> <BR>> asterisk-dev mailing list<BR>> To UNSUBSCRIBE or update options visit:<BR>> http://lists.digium.com/mailman/listinfo/asterisk-dev<BR><BR><br /><hr /> <a href='' target='_new'></a></body>
</html>