Well, technically speaking, the remote end should _not_ send a 180 after a 200. But then it seems like it's traditionally FS' job to adapt to faulty gws.

Take a look at https://freeswitch.org/confluence/plugins/servlet/mobile#content/view/6587394 you may find some answers there.

Good luck.

On Thursday, October 11, 2018, Mody, Darshan (Darshan) <darshanmody@avaya.com> wrote:

Hi

 

We are running UDP traffic. During heavy load FS receives sometimes receives 180 response after 200 OK already received on the same call-id (dialog). However FS does not discard the same and starts processing 180 even though it has already received 200 OK on the same call-id (dialog).

 

Freeswitch should be discarding the 180 response after it gets 200 OK response from far-end.

 

In our case the FS core state machine even though it gets 200 OK waits for 200 Ok again.

 

Thanks

Darshan

--

Regards,

David Villasmil

email: david.villasmil.work@gmail.com

phone: +34669448337

_________________________________________________________________________
Professional FreeSWITCH Services
sales@freeswitch.com
https://freeswitch.com

Official FreeSWITCH Sites
https://freeswitch.com/oss
https://freeswitch.org/confluence
https://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
https://freeswitch.com