200 OK is a proper respond in this scenario as FS did receive the Update for an existing SIP session. Codec negotiation is a different story and is negotiated through SDP (Offer/Answer). 

If FS responds with a 4XX response code, the call would very likely be dropped which probably be a less desired outcome.

Regards,
Ali Pey
 


On Mon, Dec 30, 2013 at 12:04 PM, gegetel <geo.cherchetout@laposte.net> wrote:
Le 30/12/2013 15:48, *Ali Pey* wrote:
> Hello,
>
> As you can see, the 200 OK message to the Update does not include t.38. So,
> this would be a bug on your service provider if they continue to do t.38.

I saw this message does not include t.38 and whas suspecting my provider's
behaviour to be wrong. Now I am sure.
But is "OK" the best answer to an *only t.38* request ? Is not there a way
to have FreeSwitch rejecting more firmly such a request ?

> Almost all service providers have the ability to turn off t.38 per account.
> I'd suggest you talk to your service provider.

OK, I am preparing a complaint with, now, one more strong argument. Not sure
to be proved right because I am a very small customer...

Thank you very much for your answer.


_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org