Hi Bastien,

If you see incoming and outgoing udptl traffic on both SIP-FAX devices, capture it and load the file on wireshark. Check the T.38 signaling and see where it is failing and why. As an example/reference, use a capture from a working case.

Regards, Ovidiu Sas

On 11/17/06, Bastian Schern ml02@in-bln.de wrote:

Hi Bogdan,

I think it has nothing to do with a deadlock. I see the incoming and outgoing UDPTL traffic on both SIP-FAX devices.

Do you got a suggestion for me, what I could do to locate and resolve the problem.

Cheers Bastian

--On Donnerstag, 16. November 2006 14:12 +0200 Bogdan-Andrei Iancu bogdan@voice-system.ro wrote:

...

Hi Bastin,

probably there is kind of a RTP deadlock between the RTPproxy and OpenPBX - both are waiting for the other party to send the media before sending on its turn.

try something like: if (nat_uac_test("8")) { force_rtp_proxy(); } else { force_rtp_proxy("r"); }

refer to http://www.openser.org/docs/modules/1.2.x/nathelper.html for more details.

regards, bogdan

Bastian Schern wrote:

...

Hi everybody,

I've got a question: Does anybody get T.38 working between OpenPBX and OpenSER + RTPProxy?

The following scenarios are working fine:

1: SIP-FAX1 (pub. IP) <-> OpenPBX <-> SIP-FAX2 (pub. IP) 2: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (pub. IP) 3: SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> SIP-FAX2 (NAT) 4: SIP-FAX1 (pub. IP) <-> OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP)

But the following scenario is not working:

SIP-FAX1 (NAT) <-> RTPProxy+OpenSER <-> OpenPBX <-> SIP-FAX2 (pub. IP)

It seems to be that the RTPproxy has a problem with the OpenPBX but no Problem with SIP-FAX-ATAs.

Does anybody have an idea what's going wrong???

Cheers Bastian

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users

---

Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users