Could you try another SIP provider like sip.antisip.com for the 16k codec?
On Sat, May 15, 2010 at 12:23 PM, Grant <[email protected]> wrote:
> > If it is a sample rate issue you may try different audio codecs for
> > different sample rates. Enable just one codec that uses the rate you are
> > currently testing...
> > Dragos
>
> When I enable only the 16k codec I get "Not acceptable here". When I
> enable only the 8k codecs the call goes through but there is no input
> or output to/from the headset. I do hear a click noise in the headset
> when the call is initiated though. I've also tried setting the
> bluetooth device in a plug in asound.conf and selecting the plug
> device but the result is the same.
>
> - Grant
>
>
> >> > >> >> My bluetooth headset works in twinkle and aplay, and I've been
> >> > >> >> trying
> >> > >> >> all day to get it to work in linphone with no luck.
> >> > >> >>
> >> > >> >> I've added this to /etc/asound.conf:
> >> > >> >>
> >> > >> >> pcm.bluetooth {
> >> > >> >> type bluetooth
> >> > >> >> device 00:11:22:33:44:55
> >> > >> >> }
> >> > >> >>
> >> > >> >> and this to .linphonerc:
> >> > >> >>
> >> > >> >> alsadev=pcm.bluetooth
> >> > >> >>
> >> > >> >> I can select "pcm.bluetooth" in linphone but it doesn't produce
> or
> >> > >> >> capture any sound. Does anyone have any suggestions?
> >> > >> >>
> >> > >> >> - Grant
> >> > >> >
> >> > >> > I should also mention that I get errors like these in dmesg:
> >> > >> >
> >> > >> > hci_scodata_packet: hci0 SCO packet for unknown connection handle
> 0
> >> > >> > btusb_isoc_complete: hci0 corrupted SCO packet
> >> > >> > btusb_bulk_complete: hci0 urb failed to resubmit (19)
> >> > >> > btusb_send_frame: hci0 urb submission failed
> >> > >> >
> >> > >> > - Grant
> >> > >>
> >> > >> No ideas on this at all? Is anyone using linphone with a bluetooth
> >> > >> headset?
> >> > >
> >> > > The little experience I have with bluetooth headsets is on Openmoko,
> >> > > and
> >> > > that has unusual bluetooth audio routing. I have 'profile "auto"'
> >> > > after
> >> > > the 'device' line in asound.conf but I don't know if it's necessary.
> I
> >> > > haven't tried it with linphone yet.
> >> > >
> >> > > The errors look like driver errors. I don't know what linphone might
> >> > > be
> >> > > doing to provoke them though.
> >> >
> >> > The bluetooth headset works perfectly in skype so it's definitely a
> >> > linphone issue. Any other ideas on this?
> >>
> >> You're assuming they have identical access patterns. Say the driver
> >> advertises
> >> two sample rates, but only supports one of them. Skype requests the
> >> working
> >> one, and linphone requests the broken one. Skype works, linphone
> doesn't,
> >> but
> >> the bug is in the driver. I'm not saying that's what's happening here,
> but
> >> the
> >> messages you report are at the driver level. We don't have evidence yet
> to
> >> show whether linphone is causing this by behaving incorrectly, or
> whether
> >> it
> >> is doing everything as it should but in an unusual way that provokes a
> bug
> >> in
> >> the driver.
>
> _______________________________________________
> Linphone-users mailing list
> [email protected]
> http://lists.nongnu.org/mailman/listinfo/linphone-users
>
_______________________________________________
Linphone-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/linphone-users
