asterisk users - Aug 2005 - Audio Problem when zaptel modules are loaded

Hello, I have an Asterisk @ Home box up and running.  I'm trying to 
prepare the box to be the phone system in our new office.

I have 3 Polycom 500's with the latest SIP firmware and all is fine, I 
can call Asterisk, check my voicemail, call the other handsets, transfer 
call, even make calls to the PSTN via voipjet.  So I'm doing ok.  The 
problem I have now is that when I reboot into a kernel that has the 
zaptel modules compiled for it, then I can no longer call asterisk 
server and hear anything.  I can however still call the PSTN via voipjet 
and I can call the other phones.

When you look at the * log output below the only thing that I see as 
potentially relevant  is the fact that when I can't hear the vm-login, 
there is a "Scheduling timer at 160 sample intervals" just before it, 
but when it works, there is not. 

Any ideas?  Thanks,

Matt


   1.
      This first log excerpt is when I boot into a linux kernel that has
      the zaptel drivers installed, this results in asterisk not being
      able to play sound to me, so I can't hear the vm-login recording.
   2.
      Aug 26 15:58:18 DEBUG[2856]: Setting NAT on RTP to 0
   3.
      Aug 26 15:58:18 DEBUG[2856]: Stopping retransmission on
      '5a108cbb-4ad81ef5-bf876d0a@192.168.3.201' of Response 1: Found
   4.
      Aug 26 15:58:18 DEBUG[2856]: Setting NAT on RTP to 0
   5.
      Aug 26 15:58:18 DEBUG[2856]: Check for res for 201
   6.
      Aug 26 15:58:18 DEBUG[2856]: Call from user '201' is 1 out of 0
   7.
      Aug 26 15:58:18 DEBUG[2856]: build_route: Contact hop:
      <sip:201@192.168.3.201>
   8.
      Aug 26 15:58:18 VERBOSE[2856]:     -- Executing
      Answer("SIP/201-ec07", "") in new stack
   9.
      Aug 26 15:58:18 VERBOSE[2856]:     -- Executing
      Wait("SIP/201-ec07", "1") in new stack
  10.
      Aug 26 15:58:18 DEBUG[2856]: Stopping retransmission on
      '5a108cbb-4ad81ef5-bf876d0a@192.168.3.201' of Response 2: Found
  11.
      Aug 26 15:58:19 VERBOSE[2856]:     -- Executing
      VoiceMailMain("SIP/201-ec07", "default") in new stack
  12.
      Aug 26 15:58:19 DEBUG[2856]: Ooh, format changed from unknown to ulaw
  13.
      Aug 26 15:58:19 DEBUG[2856]: Scheduling timer at 160 sample intervals
  14.
      Aug 26 15:58:19 VERBOSE[2856]:     -- Playing 'vm-login' (language
      'en')
  15.
       
  16.
      This next excerpt is from a different kernel on the same box that
      doesn't have the zaptel driver compiled, here the sound works
      find, and I can here the vm-login recording:
  17.
      Aug 26 16:07:05 DEBUG[2820]: Manager received command 'Command'
  18.
      Aug 26 16:07:05 DEBUG[2820]: Manager received command 'Command'
  19.
      Aug 26 16:07:31 DEBUG[2820]: Setting NAT on RTP to 0
  20.
      Aug 26 16:07:31 DEBUG[2820]: Stopping retransmission on
      '4b8b0eed-75aefca3-36ccacb8@192.168.3.205' of Response 1: Found
  21.
      Aug 26 16:07:31 DEBUG[2820]: Setting NAT on RTP to 0
  22.
      Aug 26 16:07:31 DEBUG[2820]: Check for res for 205
  23.
      Aug 26 16:07:31 DEBUG[2820]: Call from user '205' is 1 out of 0
  24.
      Aug 26 16:07:31 DEBUG[2820]: build_route: Contact hop:
      <sip:205@192.168.3.205:5060>
  25.
      Aug 26 16:07:31 VERBOSE[2820]:     -- Executing
      Answer("SIP/205-6859", "") in new stack
  26.
      Aug 26 16:07:31 VERBOSE[2820]:     -- Executing
      Wait("SIP/205-6859", "1") in new stack
  27.
      Aug 26 16:07:31 DEBUG[2820]: Stopping retransmission on
      '4b8b0eed-75aefca3-36ccacb8@192.168.3.205' of Response 2: Found
  28.
      Aug 26 16:07:32 VERBOSE[2820]:     -- Executing
      VoiceMailMain("SIP/205-6859", "default") in new stack
  29.
      Aug 26 16:07:32 DEBUG[2820]: Ooh, format changed from unknown to ulaw
  30.
      Aug 26 16:07:32 VERBOSE[2820]:     -- Playing 'vm-login' (language
      'en')
  31.
      Aug 26 16:07:35 WARNING[2820]: Couldn't read username
  32.
      Aug 26 16:07:35 VERBOSE[2820]:   == Spawn extension
      (from-internal, *98, 3) exited non-zero on 'SIP/205-6859'
  33.
      Aug 26 16:07:35 VERBOSE[2820]:     -- Executing
      Macro("SIP/205-6859", "hangupcall") in new stack
  34.
      Aug 26 16:07:35 VERBOSE[2820]:     -- Executing
      ResetCDR("SIP/205-6859", "w") in new stack
  35.
      Aug 26 16:07:35 DEBUG[2820]: cdr_mysql: inserting a CDR record.
  36.
      Aug 26 16:07:35 DEBUG[2820]: cdr_mysql: SQL command as follows: 
      INSERT INTO cdr
     
(calldate,clid,src,dst,dcontext,channel,dstchannel,lastapp,lastdata,duration,
  37.
      billsec,disposition,amaflags,accountcode) VALUES ('2005-08-26
      16:07:31','\"205Poly500\"
<205>','205','*98','from-internal',
      'SIP/205-6859','','ResetCDR','w',4
  38.
      ,4,'ANSWERED',3,'')
  39.
      Aug 26 16:07:35 VERBOSE[2820]:     -- Executing
      NoCDR("SIP/205-6859", "") in new stack
  40.
      Aug 26 16:07:35 WARNING[2820]: CDR on channel 'SIP/205-6859' not
      posted
  41.
      Aug 26 16:07:35 WARNING[2820]: CDR on channel 'SIP/205-6859' lacks
end
  42.
      Aug 26 16:07:35 VERBOSE[2820]:     -- Executing
      Wait("SIP/205-6859", "5") in new stack
  43.
      Aug 26 16:07:35 VERBOSE[2820]:   == Spawn extension
      (macro-hangupcall, s, 3) exited non-zero on 'SIP/205-6859' in
      macro 'hangupcall'
  44.
      Aug 26 16:07:35 VERBOSE[2820]:   == Spawn extension
      (from-internal, h, 1) exited non-zero on 'SIP/205-6859'
  45.
      Aug 26 16:07:35 DEBUG[2820]: update_user_counter(205) - decrement
      inUse counter
  46.
       
  47.
      Why would the zaptel drivers effeect this?