On 03/06/2011 10:52 PM, Iñaki Baz Castillo wrote:
2011/3/6 Jeff Pylejp...@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
2011/3/7 Saúl Ibarra Corretgé s...@ag-projects.com:
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
On 3/7/11 12:12 AM, Jeff Pyle wrote:
As I said I've never seen a T.38 session start without a reinvite. I
have seen only unsupported codecs come in. In a reinvite scenario, this
will cause a 488. On an initial INVITE, however, the Adtrans send a 415
Unsupported media type. I don't have
2011/3/6 Jeff Pyle jp...@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'
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
@lists.opensips.orgmailto:users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] Stopping a T.38 reinvite with Opensips
loose_route()
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
