we are using siproxd 0.7.1 and it worked all in all very fine. In some cases we have the problem that if you off hook the telephone the first one or two second is lost. So the person who called you, can´t hear your name. After that the voice quality is very fine and you can talk/phone as normal.
i turned dejitter off and the voice quality increase. also the short break appears less, but from time to time it comes beak. i am not sure if this helps but i increase the real time priority of siproxd with "rtprio"
Makes it sense to increase Real Time Priority?
Are they more configuration items to avoid the short break?
Is there a realationship between the connected ATA and the dialtime? Or could the time decrease where siproxd search for the right entry? All ATA use the same provider sipgate.
thanks,
laslo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
we are using siproxd 0.7.1 and it worked all in all very fine. In some cases we have the problem that if you off hook the telephone the first one or two second is lost. So the person who called you, can´t hear your name. After that the voice quality is very fine and you can talk/phone as normal.
OS: FeeBSD 6.2
Siproxd Version: 0.7.1-4788
Libosip: 2-3.1.0
Network:
ATAHT286---CPE-------wlan-----------AP------lan--------SIPROXD------inet-Router(with Port Forward to the SIPROXD RTP and SIP)---------inet
Provider: sipgate.de
If i missed something really needed please give me a hint.
thanks,
laslo
djitter Value is: 100000 (maybe ist too high?)
No hints for that problem?
I you do not depend on siproxd buffering ("dejittering") the RTP data you may want to turn of the dejitter feature, this should help:
rtp_input_dejitter = 0
rtp_output_dejitter = 0
/Thomas
thanks for the reply.
i turned dejitter off and the voice quality increase. also the short break appears less, but from time to time it comes beak. i am not sure if this helps but i increase the real time priority of siproxd with "rtprio"
###################################################
last pid: 70984; load averages: 0.04, 0.07, 0.03 up 16+04:39:24 13:44:13
22 processes: 2 running, 20 sleeping
CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.4% interrupt, 99.6% idle
Mem: 13M Active, 680M Inact, 163M Wired, 16K Cache, 108M Buf, 109M Free
Swap: 935M Total, 935M Free
PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
1052 root 1 96 0 2196K 1672K RUN 53:29 0.00% stund
58025 root 3 20 -76 6272K 5788K kserel 2:59 0.00% siproxd
755 root 1 96 0 3504K 2924K select 0:49 0.00% sendmail
765 root 1 8 0 1388K 1104K nanslp 0:08 0.00% cron
597 root 1 96 0 1376K 1028K select 0:04 0.00% syslogd
700 root 1 96 0 1288K 824K select 0:02 0.00% usbd
759 smmsp 1 20 0 3384K 2792K pause 0:01 0.00% sendmail
70964 root 1 96 0 6252K 3308K select 0:00 0.00% sshd
749 root 1 96 0 3524K 2708K select 0:00 0.00% sshd
70980 root 1 20 0 4812K 2960K pause 0:00 0.00% csh
808 root 1 5 -4 1752K 1388K ttyin 0:00 0.00% login
70984 root 1 96 0 2332K 1576K RUN 0:00 0.00% top
811 root 1 5 0 1344K 952K ttyin 0:00 0.00% getty
813 root 1 5 0 1344K 952K ttyin 0:00 0.00% getty
815 root 1 5 0 1344K 952K ttyin 0:00 0.00% getty
809 root 1 5 0 1344K 952K ttyin 0:00 0.00% getty
#################################################
Makes it sense to increase Real Time Priority?
Are they more configuration items to avoid the short break?
Is there a realationship between the connected ATA and the dialtime? Or could the time decrease where siproxd search for the right entry? All ATA use the same provider sipgate.
thanks,
laslo