[Asterisk-Dev] R1.502 of chan_zap.c kills callerid on a x101p

John Hill jhill at noach.com
Wed Sep 14 08:20:26 MST 2005


 

> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com 
> [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of 
> Tony Mountifield
> Sent: Wednesday, September 14, 2005 8:55 AM
> To: asterisk-dev at lists.digium.com
> Subject: [Asterisk-Dev] Re: PLEASE HELP!! CALLERID FAILS!!
> 
> In article <200509141334.j8EDXt9e032199 at commserver.noach.com>,
> John Hill <jhill at noach.com> wrote:
> > I did a make update for zaptel, libpri and asterisk. Then 
> recompiled.
> > I no longer get an error message. Callerid is still blank. 
> > The log and cli return this line:
> > Sep 14 08:22:51 NOTICE[13266]: chan_zap.c:5946 ss_thread: 
> Got event 18 (Ring
> > Begin)... 
> > 
> > I was getting a checksum error and a mylen <0 error. IT 
> would say callerid
> > failed: success.
> > 
> > 
> > I deleted all modules and did a make install of the beta1 
> source using the
> > cvshead of zaptel and libpri.
> > Caller id then works fine? 
> > 
> > Something has changed in the asterisk code that is not 
> seeing callerid from
> > of my x101p. 
> > 
> > I'm stumped!
> 
> It's almost certainly something in chan_zap.c that's changed.
> 
> Well 1.2beta1 uses r1.490 of chan_zap.c, and the latest head 
> uses r1.511.
> Try different versions of chan_zap.c (assuming there are not 
> interdependent
> changes elsewhere) using "cvs update -r1.xxx chan_zap.c" and 
> then compiling.
> The you can home in to which change stopped it working, and 
> report what
> you find as a bug.
> 
> If there are interdependent changes, you will have to try 
> checking out the 
> whole tree at specific dates using the update or checkout 
> option -Dyyyy-mm-dd
> 
> You can look for likely starting points with "cvs log chan_zap.c".
> 
> Hope this helps!
> 
> Cheers
> Tony

Found it:

R1.502 of chan_zap.c kills callerid on a x101p.

add new channel option (via ast_channel_setoption()) to let channel drivers
adjust txgain/rxgain if they are able (only Zap channels at this time)
modify app_chanspy to use new gain option
reformat app_chanspy to match coding guidelines
add user-controlled volume adjustment to app_meetme (issue #4170, heavily
modified to actually work on Zap channels)

I have never filed a bug report. I'll give it a try?

--john






More information about the asterisk-dev mailing list