Christopher Aloi wrote: > Thanks for the update. > > Unfortunately that will not work in my scenario. > > Here's what I need: > > OPBX --> INVITE with SDP (G711+T38 ability) > GW --> OPBX > 200 > 180 > Media Starts > GW --> OPBX T38 Request > 200 > T38 Starts > > When calling T38TXDETECT=something OPBX sends the second invite > including T38 (which the GW rejects with a 488) It sounds like your gateway is not prepared to do T.38, though it is normally the called party that re-invites for T.38 mode.
> > When calling Set: T38CALL=1 OPBX sends the T38 SDP in the first > invite; which the GW also rejects with a 488 It definitely sounds like your gateway is not prepared to do T.38. A call is most definitely allowed to start in T.38 mode. > > When not calling either of the above OPBX and the GW negotiate and > send the fax using G711. Correct. > > Per the spec outlined in " > http://tools.ietf.org/wg/sipping/draft-ietf-sipping-realtimefax/draft-ietf-sipping-realtimefax-01.txt"; > > A T38 negotiation should follow the inital flow I outlined above. > > Has anyone been able to get T38 to come up on a RE-INVITE from the GW > to OPBX? What you described above is one of several valid scenarios described in the T.38 spec and the document you quoted. The scenario where the call starts in T.38 mode should definitely work, though, unless your gateway is broken. Sadly, many are. If we find too much trouble of this kind, we may need to make things more tolerant. Regards, Steve _______________________________________________ Openpbx-users mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-users
