[OpenSIPS-Users] Stopping a T.38 reinvite with Opensips loose_route()

[Dave Singer]

JP,

The two end points have to agree on an RTP protocol.
You may look at the SDP in the initial INVITEs to see if T.38 is offered and
if it is, remove it.
Also if the re-INVITE contains G711 along with the T.38 you should be able
to just remove the T.38.
That should accomplish the same effect as the customer disabling T.38.

FYI: FaxBack has a very reliable T.38 implementation NET SatisFAXtion that
we have been using for quite some time.

Dave

On Sun, Mar 6, 2011 at 1:52 PM, Iñaki Baz Castillo <ibc at aliax.net> wrote:

> 2011/3/6 Jeff Pyle <jpyle at fidelityvoice.com>:
> > Unfortunately the customer cannot disable T.38.  I'd like to be able to
> > reject the reinvite with a send_reply("488", "Not acceptable here")
> within
> > the loose_route() section.  Is this legit, or am I going to break things,
> > like getting the two endpoints' CSeqs out of sync?
>
> You are not going to break CSeq at all. The proxy is able to reject
> in-dialog requests depending on local policy. When the UA receives 488
> it does know that, in case of a new in-dialog request, it must use a
> greater CSeq, which of course will be valid in the other UA (it must
> be just higher than previous one, no matter how much higher).
>
> But in your case, the problem is that when your UA receives the 488 it
> will probably send a BYE (it's the usual policy when a re-INVITE is
> rejected). But you can try it. You will not break SIP protocol at all.
>
> --
> Iñaki Baz Castillo
> <ibc at aliax.net>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20110306/b7d70611/attachment.htm>