Tzafrir Cohen wrote:
> On Mon, Feb 09, 2009 at 06:40:29PM +0000, Julien Levi wrote:
>   
>> Hello,
>>
>> I'm trying to use the asterisk packages for Debian lenny with a 
>> junghanns quadgsm card. Everything appears to have installed correctly 
>> but I can't get asterisk to recognise the card. Things fall apart when 
>> asterisk tries to load chan_zap - it fails with the message:
>>
>>   == Registered application 'ZapSendKeypadFacility'
>>   == Parsing '/etc/asterisk/zapata.conf': Found
>> [Feb  9 18:29:51] ERROR[2487]: chan_zap.c:12277 process_zap: Unknown 
>> signalling method 'gsm'
>> [Feb  9 18:29:51] ERROR[2487]: chan_zap.c:11831 build_channels: 
>> Signalling must be specified before any channels are.
>>
>> This suggests to me that asterisk hasn't been compiled with full libgsm 
>> support, but I'm no expert. Everything else seems OK config wise.
>>
>> Output of ztcfg:
>>
>> PBX1:~# ztcfg -v
>>
>> Zaptel Version: 1.4.11
>> Echo Canceller: MG2
>> Configuration
>> ======================
>>
>> SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)
>> SPAN 2: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)
>> SPAN 3: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)
>> SPAN 4: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)
>>
>> 8 channels to configure.
>>
>> I'm using the example zapata.conf.quadGSM as my zapata.conf. Has the 
>> keyword for gsm signalling changed? Have I made an error in my 
>> configuration.
>>     
>
> I don't think it has ever worked. For the simple fact that nobody
> bothered building libgsmat in a package. And, well, also due to the fact
> that nobody really seems to have needed it.
>
> Sometime at the Lenny cycle Faidon Liambotis broke the big Asterisk
> bristuff patch to smaller pieces. Only then have we managed to have a
> separate Zaptel/GSM patch . 
>
> And at about that point I realised that we never got to add libgsmat to
> Debian. I generally have a package waiting in the pkg-voip repo, but I
> never bothered building it because nobody seems to have needed it (e.g.
> complained that the Etch package was broken). I don't really like
> maintaining software I can't test.
>
> Sadly in the recent year or so I have not been able to feed patches
> easily to K.P. Junghanns (as in: my emails and calls did not bring about
> any reply) and thus I suppose that my small fixes to the libgsmat
> Makefile have not made it upstream. Specifically minor tweaks for
> building with a DESTDIR are needed. This was fixed lately in my copy at
> http://updates.xorcom.com/astribank/bristuff/1.4/
>
> So in short: want to start testing GSM support?
>
> That said: for the 1.6 packages I don't intend to use bristuff, as many
> of the important features are already included in 1.6, and
> forward-porting the bristuff libpri patch to libpri 1.4.4 seems quite
> difficult. Not to mention the general pain of maintaining bristuff.
>
> So I'm not sure that this is getting into any newer packages in the long
> run. If you know K.P. Junghanns's opinion on this, I would appreciate to
> hear or read it.
>   

I'd be happy to test GSM support. Can you provide a ready built package 
or would I need to build it myself after applying a libgsmat patch? 
Since I'll have to build asterisk from source anyway to get the card 
working,  I'd prefer to do it the "debian way" and have it play nicely 
with the rest of the system. As lenny is frozen, if it works 
satisfactorily would you be willing to host the resultant package?

_______________________________________________
Bristuff-users mailing list
[email protected]
http://lists.three-dimensional.net/mailman/listinfo/bristuff-users

Reply via email to