Mark, somehow I missed the replies to my original email and just stumbled
across them on the list archives.
The problem in the situation below is that there is jitter between SER and
Asterisk. Since Asterisk doesn't compensate for this, the person on the other
end of a call with one of our PAP2-NA customers hears choppiness. The jitter
buffer on the PAP2-NA helps deal with any jitter in the other direction.
Just trying to figure out if indeed rtpproxy or mediaproxy have a jitter
buffer built in. I could potentially throw another SER install nearer to the
Asterisk box to deal with the jitter and then hand off to Asterisk.
I'd love to get Asterisk completely out of the media path and just use it for
centralized call routing, voicemail, etc, but I'm not sure how to tell
Asterisk to tell other SIP clients to use my SER boxes for the media path
instead. In any case, that's a question for the Asterisk list. :-)
Basically.. anyone know if rtpproxy and/or mediaproxy have jitter buffers? :)
Ray
On Wed, Sep 21, 2005 at 09:19:53AM -0700, Ray Van Dolson wrote:
First off, here is my voice network layout currently:
http://webdev.digitalpath.net/~rayvd/voice/voice_network2.png
We're using Asterisk for voicemail, call routing (for long-distance, LNP, etc)
and SER/rtpproxy at the other end which handles NAT onto private networks
where customer's exist.
This setup works fairly well for the most part, except that Asterisk does not
have a jitter buffer. I would like to make use of rtpproxy (or mediaproxy)
for their jitter buffer on both ends of our voice links here. To me, that
would mean shoving a SER/rtpproxy combo between Asterisk and our provider
network. Possibly on the same server.
I could easily throw up a SER installation, but I'm trying to figure out if
there's any way to leave Asterisk in the SIP path but remove it from the media
path (have RTP just go straight from SER/rtpproxy to my provider's RTP proxy).
Have any of you set up a scenario somewhat like this? Any recommendations?
Asterisk CVS-HEAD does let you apply a patch and get some very alpha jitter
buffer support. But CVS HEAD doesn't work reliably for me at all currently so
I'm sticking with the latest stable release of 1.0.x series.
I'm running SER 0.9.3 FYI on the SER proxies I have set up currently.
Thanks.