#11 Call Fails on Avaya System

[Pete Davidson]

Setup:

Avaya System (172.26.195.72 and 172.26.195.75) with two MPF\'s running ptlib/opal/t38modem (sender 172.26.195.50, receiver 172.26.195.52)

ptlib and opal at rev 24174. t38modem at current trunk.

Call fails when receiver gets +FCERROR to the AT+FRH=3 command when trying to receive DCS. Looks like to me that t38modem receives all packets for the DCS, but does not send them up. It then sends +FCERROR when the V.17 data comes.

I am attaching wireshark trace, and +ttttt t38modem traces from sender and receiver.

[Pete Davidson]

network trace and 2 t38trace log files

[Vyacheslav Frolov]

The receiver sends DIS and waits DCS.
The sender receives DIS and sends DCS.

The receiver does not gets DCS (it gets +FCERROR to the AT+FRH=3 because it lose first two UDPTL packets because of seq_number is not synchronized).
Usualy it's not a problem and should be recovered while reiteration.

The receiver sends DIS and waits DCS (again).
The sender receives DIS and sends DCS:

2010/07/29 11:25:08.133 Media Patch:0x206574f0 T38_UDPTL Encoded transmitted UDPTL data :
{
seq_number = 92
...

But receiver does not receive nothing:

2010/07/29 11:25:07.635 ptyp3(e):5...0x204174f0 --> AT+FRH=3
...
2010/07/29 11:25:13.432 ptyp3(e):5...0x204174f0 Reset state stRecvBegWait

It looks like Avaya System was discouraged by DIS/DCS reiteration.

Try update Avaya System.
Try t38modem 2.0.

[SourceForge Robot]

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).