Rich Adamson
2005-Oct-07 06:12 UTC
[Asterisk-Users] Distorted VM with iax2 with ilbc and jitterbuffer - bug?
Two asterisk boxes 150 miles apart, both cvs-head as of this morning (and since Sept 27th), connected via iax2 with low-utilized ds3 internet, C7960 calls exten on remote system (also C7960), and call goes to VM. No other calls in either system (eg, no load). Both boxes have iax config'ed as: trunk=yes allow=ilbc jitterbuffer=yes Recorded VM messages are very distorted. Changing only jitterbuffer=no (and * restart), recorded VM messages are very clean. With jitterbuffer=yes and trunk=no, messages are very clean. Both boxes config'ed as: trunk=yes allow=gsm jitterbuffer=yes Recorded VM messages are very clean. Conclusion: looks like the combination of trunk=yes and jitterbuffer=yes with ilbc is causing the distorted VM messages. Normal answered calls have no distortion. Is this an unacceptable iax config or does this represent a bug? (Problem can be recreated at will and is very consistent.) Rich
Steve Kann
2005-Oct-07 08:04 UTC
[Asterisk-Users] Distorted VM with iax2 with ilbc and jitterbuffer - bug?
Rich Adamson wrote:>Two asterisk boxes 150 miles apart, both cvs-head as of this morning >(and since Sept 27th), connected via iax2 with low-utilized ds3 internet, >C7960 calls exten on remote system (also C7960), and call goes to VM. >No other calls in either system (eg, no load). > >Both boxes have iax config'ed as: > trunk=yes > allow=ilbc > jitterbuffer=yes >Recorded VM messages are very distorted. > >Changing only jitterbuffer=no (and * restart), recorded VM messages are >very clean. With jitterbuffer=yes and trunk=no, messages are very clean. > >Both boxes config'ed as: > trunk=yes > allow=gsm > jitterbuffer=yes >Recorded VM messages are very clean. > >Conclusion: looks like the combination of trunk=yes and jitterbuffer=yes >with ilbc is causing the distorted VM messages. Normal answered calls >have no distortion. > >Is this an unacceptable iax config or does this represent a bug? >(Problem can be recreated at will and is very consistent.) > > >Try using trunktimestamps as well..