Juha Heinanen writes: > why is sems selecting speex/8000 instead of proposed speex/32000?
answering to myself, the reason seems to be that sems speex does not support ultra wideband speex at 32000hz, but it does support 8000hz and 16000hz frequencies. when i changed twinkle to advertises all three frequencies, sems correctly picked 16000hz frequency: v=0 o=twinkle 2130875533 1433938545 IN IP4 192.168.0.169 s=- c=IN IP4 192.168.0.169 t=0 0 m=audio 8000 RTP/AVP 99 98 97 8 0 3 101 a=rtpmap:99 speex/32000 a=rtpmap:98 speex/16000 a=rtpmap:97 speex/8000 a=rtpmap:8 PCMA/8000 ... v=0 o=sems 233957345 908400434 IN IP4 192.98.100.34 s=sems c=IN IP4 192.98.100.34 t=0 0 m=audio 40006 RTP/AVP 98 97 8 0 3 101 a=rtpmap:98 speex/16000 a=rtpmap:97 speex/8000 ... i also tested sems silk codec against baresip, and it worked fine at 24000hz frequency. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
