Armin Schindler wrote:
> 
> chan_capi speaks alaw (or ulaw) only, which is set in 
> writeformat/readformat. This works with older Asterisk perfectly. But 
> with current OpenPBX I get an error when calling SIP/IAX2 which allow
> gsm only. According to the debug log, the formats are set correctly, but
> OpenPBX is sending frames with subclass 'slin' to chan_capi->write instead 
> of alaw.
> 

I may be wrong, but isn't it necessary to match the ulaw/alaw format of 
CAPI to the telco? ie. for ETSI it will be alaw, for North America it 
will be ulaw?

I have a problem which may or may not be related to what you describe 
above anyway. I've got OpenPBX SVN-1137 working quite well with an Eicon 
Divas 4-port BRI card - simple in/out calling works fine. If an incoming 
CAPI call hits a SIP phone, and that call is answered and then 
transferred to another SIP phone, the original PSTN caller hears 
extremely choppy/garbled/unintelligible sound, but the SIP callee can 
hear the PSTN caller perfectly. Up until the transfer however, the sound 
is fine, both ways. The SIP phone (Grandstream GXP2000) shows the codec 
as alaw (since we are ETSI in NZ), which is fine because the GXP2000 is 
configured for either a/ulaw.

Obviously this is a show-stopper for us, and tonight I had to abort the 
PBX cutover and regress to their existing hardware PBX :(
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev

Reply via email to