rtpproxy works very well with T.38 (the transport protocol for T.38 is
udptl built on top of udp just like rtp).
Jens, which version of rtpproxy do you use?
On Fri, Aug 1, 2008 at 2:49 PM, Alex Balashov <abalashov(a)evaristesys.com> wrote:
T.38 is not RTP, so I am not sure why one would expect
them to be relayed.
Jens Carl wrote:
Hello List,
I have problem with T.38 and the RTPproxy by one of mine scenarios.
The first one works flawless and looks like that:
Linksys ATA -> NAT -> OpenSer/RTPproxy -> T.38-GW (Asterisk)
The second one on the other hand don't work how it should and looks like
this one:
T.38-GW -> SIP-Proxy -> Openser/RTPproxy -> NAT -> Linksys ATA.
The normal RTP stream is opened and they switch over to T.38, but the
RTPproxy isn't sending out the received T.38 packets from the ATA.
If the OpenSER is getting a re-INVITE I call the function
force_rtp_proxy(). I already tried the function with 'l' parameter but
then none of the scenarios are working.
Why is the RTPproxy not relaying like in the 1st scenario?
Which flag should I use to get the things working?
Why is RTPproxy using the same ports like it used for the normal RTP
traffic?
I thought when I call force_rtp_proxy() a 2nd time I create a new
session with different ports?
Can I force the RTPproxy to use different ports?
If someone needs a PCAP-trace I can provide this.
Many thanks
Jens
_______________________________________________
Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
--
Alex Balashov
Evariste Systems
Web :
http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (706) 338-8599
_______________________________________________
Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users