On Mon, 19 Dec 2005, Daniel Swarbrick wrote:
> Armin Schindler wrote:
> > 
> > I can confirm this problem. When two sides use different codecs then the
> > transcodec stuff seems to be messed up.
> > 
> > Someone here with more knowledge about 'how this works on openpbx' ?
> > 
> > Armin
> 
> I'm glad somebody else is able to reproduce this problem. Which are the two
> different codecs you refer to? In my setup, I had the ISDN DID Dial()'ing a
> SIP channel (Snom 220 phone). The call should have come in from CAPI as alaw,
> hit the Snom 220 (which supports alaw/ulaw among others), then it was
> transferred to a Grandstream GXP2000 (also supports alaw/ulaw). The display on
> the GXP2000 showed the codec in use was alaw.
> 
> So, it should have been alaw all the way through.
> 
> PS: beware, Grandstream phones/ATA's do NOT support SIP reinvite, so the PBX
> will proxy all calls (even if it doesn't have to transcode).

I have a different setup. One side is ISDN (alaw) and the other side is SIP
with a Grandstream BT100.
1) sip.conf: gsm only
   a) SIP -> CAPI: refused with 'No compatible codecs'
      This seems to be right, because Grandstream does not support GSM!?
   b) CAPI-> SIP : voice connection is made, but no sound. 'sip show 
      channels' reports ulaw !!!
2) sip.conf: ilbc only
   a) SIP -> CAPI: voice works, but console reports some warnings about
      ilbctoslin gets wrong frame size.
   b) CAPI-> SIP : voice doesn't work and the ilbctoslin warnings don't 
      stop.
3) sip.conf: allow alaw as well
   Voice works in one direction only. I didn't test the transfer, since
   the problem is there from the beginning.

Any hint where to dig? 
I will try to find out more, maybe with some more debug...

Armin
_______________________________________________
Openpbx-dev mailing list
[email protected]
http://lists.openpbx.org/mailman/listinfo/openpbx-dev

Reply via email to