traud / asterisk-amr

Asterisk 13 transcoding module: AMR-WB
The Unlicense
32 stars 19 forks source link

asterisk 16.4.0 and Jitsi - AMR error #17

Closed ycaner06 closed 4 years ago

ycaner06 commented 5 years ago

Hello,

First of all , thank you for all effort.

Secondly , I installed your patch on Asterisk 16.4.0 and try to playback a record and couldnt hear any sound. How can we solve this problem .

In addition, asterisk a file converter feature that helps to convert records to another codec format. it can reachable from asterisk console as "file convert source destionation" . is there a way to run this feature for AMR /AMR-WB codecs.

Thanks for support

Information; Asterisk IP addr : 192.168.1.210 Client Ip addr: 192.168.1.17

Jitsi codec order; image

Wireshark filter; image

Asterisk console debug; Playing a record as sln16 image

SIP packet , codec order image

In addition Asterisk endpoint configuration; [ycaner] type=endpoint transport=transport-udp-v4 context=incoming auth=ycaner aors=ycaner dtmf_mode=rfc4733 rewrite_contact=yes direct_media=no disallow=all allow=amrwb allow=amr allow=g722 allow=alaw allow=ulaw contact_user=ycaner force_rport=yes ice_support=yes inband_progress=yes moh_passthrough=yes

ycaner06 commented 5 years ago

Hello, I tested on MicroSIP that is working with AMR-WB. it can play any record with sln16. Thanks

ycaner06 commented 5 years ago

I found a difference between Jitsi's and MicroSIP that is Reserved flag Jitsi's RTP packet image

MicroSIP2s RTP Packet image

image

ycaner06 commented 5 years ago

Lastly , i shared Pcap files.

Jitsi-AMR-WB.zip microsip-amr-test.zip

Opened a topic on Jitsi forum : https://community.jitsi.org/t/jitsi-destkop-couldnt-hear-amr-codec-from-asterisk/18436

traud commented 4 years ago

I am closing this issue because it is Jitsi and cannot be worked-around on the Asterisk side. Anyway, I added a fix to your thread in the Jitsi Community. If that does not fix this issue here and there is still in an issue on the Asterisk side, please, do not hesitate and reopen this issue here.