Hello, I apologize for my bad English. Three years ago there was a message http://lists.freeswitch.org/pipermail/freeswitch-users/2015-June/113829.html and here I am faced with the same problem. A stupid provider sends crypto in RTP/AVP and to ensure processing this request, I inserted in the profile the parameter NDLB-allow-crypto-in-avp=true But Freeswitch answers to INVITE inserting in OK this line: m=audio 0 RTP/AVP 19 and the provider understands this as "no audio" and does not send ACK and does not send rtp. How to deal with this I do not know. Regards. Victor Bogatyryev
sounds like a bug to me. Try master?
On Jun 27, 2018, at 3:55 AM, Victor Bogatyryev <victor.bogatyryev@gmail.com> wrote:
Hello,
I apologize for my bad English.
Three years ago there was a message http://lists.freeswitch.org/pipermail/freeswitch-users/2015-June/113829.html <http://lists.freeswitch.org/pipermail/freeswitch-users/2015-June/113829.html> and here I am faced with the same problem. A stupid provider sends crypto in RTP/AVP and to ensure processing this request, I inserted in the profile the parameter NDLB-allow-crypto-in-avp=true But Freeswitch answers to INVITE inserting in OK this line: m=audio 0 RTP/AVP 19 and the provider understands this as "no audio" and does not send ACK and does not send rtp.
How to deal with this I do not know.
Thank you, Michael, FreeSWITCH Version 1.6.19+git~20171120T163416Z~b1b21d0695~64bit I tried to make it current but failed: make[10]: Entering directory `/usr/local/src/freeswitch/libs/sofia-sip/libsofia-sip-ua/tport' LTCOMPILE tport.lo LTCOMPILE tport_logging.lo LTCOMPILE tport_stub_sigcomp.lo LTCOMPILE tport_type_udp.lo LTCOMPILE tport_type_tcp.lo LTCOMPILE tport_type_sctp.lo tport_type_sctp.c: In function 'tport_sctp_init_socket': tport_type_sctp.c:206:10: error: variable 'initmsg' has initializer but incomplete type struct sctp_initmsg initmsg = { 0 }; ^ tport_type_sctp.c:206:10: error: excess elements in struct initializer [-Werror] tport_type_sctp.c:206:10: error: (near initialization for 'initmsg') [-Werror] tport_type_sctp.c:206:23: error: storage size of 'initmsg' isn't known struct sctp_initmsg initmsg = { 0 }; ^ tport_type_sctp.c:211:36: error: 'SCTP_INITMSG' undeclared (first use in this function) if (setsockopt(socket, SOL_SCTP, SCTP_INITMSG, &initmsg, sizeof initmsg) < 0) ^ tport_type_sctp.c:211:36: note: each undeclared identifier is reported only once for each function it appears in tport_type_sctp.c:206:23: error: unused variable 'initmsg' [-Werror=unused-variable] struct sctp_initmsg initmsg = { 0 }; ^ cc1: all warnings being treated as errors make[10]: *** [tport_type_sctp.lo] Error 1 make[10]: Leaving directory `/usr/local/src/freeswitch/libs/sofia-sip/libsofia-sip-ua/tport' make[9]: *** [all] Error 2 make[9]: Leaving directory `/usr/local/src/freeswitch/libs/sofia-sip/libsofia-sip-ua/tport' make[8]: *** [all-recursive] Error 1 make[8]: Leaving directory `/usr/local/src/freeswitch/libs/sofia-sip/libsofia-sip-ua' make[7]: *** [all-recursive] Error 1 make[7]: Leaving directory `/usr/local/src/freeswitch/libs/sofia-sip' make[6]: *** [all] Error 2 make[6]: Leaving directory `/usr/local/src/freeswitch/libs/sofia-sip' make[5]: *** [/usr/local/src/freeswitch/libs/sofia-sip/libsofia-sip-ua/libsofia-sip-ua.la] Error 2 make[5]: Leaving directory `/usr/local/src/freeswitch/src/mod/endpoints/mod_sofia' make[4]: *** [mod_sofia-all] Error 1 make[4]: Leaving directory `/usr/local/src/freeswitch/src/mod' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/local/src/freeswitch/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/freeswitch' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/local/src/freeswitch' make: *** [current] Error 2 Regards. Victor Bogatyryev 11.07.2018 23:07, Michael Jerris пишет:
sounds like a bug to me. Try master?
On Jun 27, 2018, at 3:55 AM, Victor Bogatyryev <victor.bogatyryev@gmail.com <mailto:victor.bogatyryev@gmail.com>> wrote:
Hello,
I apologize for my bad English.
Three years ago there was a message http://lists.freeswitch.org/pipermail/freeswitch-users/2015-June/113829.html and here I am faced with the same problem. A stupid provider sends crypto in RTP/AVP and to ensure processing this request, I inserted in the profile the parameter NDLB-allow-crypto-in-avp=true But Freeswitch answers to INVITE inserting in OK this line: m=audio 0 RTP/AVP 19 and the provider understands this as "no audio" and does not send ACK and does not send rtp.
How to deal with this I do not know.
_________________________________________________________________________ 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
participants (2)
-
Michael Jerris
-
Victor Bogatyryev