[Kamailio-Users] T.38 not relayed by RTPproxy

[LetMeKnow]

Hello jens,


OpenSER is pure signaling to end to ends,
Can you see any T.38 header in SDP session in Linksys ATA , in invite method



Thanks &Regards
Ravi Prakash Sunkara
VoIP Development Tech Lead
91-9999882776
Josh Billings  - "There's a great power in words, if you don't hitch too
many of them together."
2008/8/1 Jens Carl <ml04 at reventix.de>

> 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 at lists.kamailio.org
> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20080801/1c609758/attachment.htm>