freeswitch-dev

Download

freeswitch-dev@lists.freeswitch.org

May 2020

2 participants
2 discussions

[Freeswitch-dev] ADD 2 ICE CANDIDATES mod_verto
by Jazmin Marina Florez Marino 02 Jun '20

02 Jun '20

Hello all, I am working with mod_verto in a scenario where I need to send public and private IP addresses as ICE candidates. When I modify the ext-rtp-ip parameter, it only sends one option as typ host ice candidate. However, for my implementation I need to send both. What I need is the combination of those ice candidates, something like this: a=candidate:8228103366 1 udp 659136 190.84.118.88 31028 typ host generation 0 a=candidate:3496438569 1 udp 659136 192.168.1.170 24210 typ host generation 0 Is it possible to add both ice candidates in the same SDP from configuration files? Thanks Jazmin Florez Marino +57 304 564 0193 Jazmin.marino(a)on24.com<mailto:Jazmin.marino@on24.com> SDP with local IP 2020-04-24 14:13:49.395900 [DEBUG] mod_verto.c:2502 Local SDP verto.rtc/5715976: v=0 o=FreeSWITCH 1587731419 1587731420 IN IP4 192.168.1.170 s=FreeSWITCH c=IN IP4 192.168.1.170 t=0 0 a=msid-semantic: WMS t9mERteVPrwT3aZbexPlp2U6Cspg78dq m=audio 24210 UDP/TLS/RTP/SAVPF 111 110 a=rtpmap:111 opus/48000/2 a=fmtp:111 useinbandfec=1; minptime=10; stereo=1; sprop-stereo=1 a=rtpmap:110 telephone-event/48000 a=silenceSupp:off - - - - a=ptime:20 a=sendrecv a=fingerprint:sha-256 FD:DF:48:02:C3:F8:D9:57:F8:C8:97:CD:3A:AB:6A:A6:97:4A:BA:A5:48:5A:3A:2D:0F:18:14:EC:D5:A9:21:86 a=setup:active a=rtcp-mux a=rtcp:24210 IN IP4 192.168.1.170 a=ice-ufrag:mScCKXydfOjcMntK a=ice-pwd:Depc4PrcDqdqfgirZlTz8iCe a=candidate:3496438569 1 udp 659136 192.168.1.170 24210 typ host generation 0 a=end-of-candidates a=ssrc:3132020181 cname:7pVPJ0AphX8bXYd1 a=ssrc:3132020181 msid:t9mERteVPrwT3aZbexPlp2U6Cspg78dq a0 a=ssrc:3132020181 mslabel:t9mERteVPrwT3aZbexPlp2U6Cspg78dq a=ssrc:3132020181 label:t9mERteVPrwT3aZbexPlp2U6Cspg78dqa0 m=video 0 UDP/TLS/RTP/SAVPF 19 2020-04-24 14:13:49.395900 [NOTICE] mod_dptools.c:1360 Channel [verto.rtc/5715976] has been answered SDP with Public IP <param name="ext-rtp-ip" value="190.84.118.88"/> 2020-04-24 14:17:23.715620 [DEBUG] mod_verto.c:2502 Local SDP verto.rtc/5715976: v=0 o=FreeSWITCH 1587724815 1587724816 IN IP4 190.84.118.88 s=FreeSWITCH c=IN IP4 190.84.118.88 t=0 0 a=msid-semantic: WMS 8gumHFWDC0sD12iPvVhSeEhUfLdXQBVO m=audio 31028 UDP/TLS/RTP/SAVPF 111 110 a=rtpmap:111 opus/48000/2 a=fmtp:111 useinbandfec=1; minptime=10; stereo=1; sprop-stereo=1 a=rtpmap:110 telephone-event/48000 a=silenceSupp:off - - - - a=ptime:20 a=sendrecv a=fingerprint:sha-256 FD:DF:48:02:C3:F8:D9:57:F8:C8:97:CD:3A:AB:6A:A6:97:4A:BA:A5:48:5A:3A:2D:0F:18:14:EC:D5:A9:21:86 a=setup:active a=rtcp-mux a=rtcp:31028 IN IP4 190.84.118.88 a=ice-ufrag:BiYFM6pSItFoUq2t a=ice-pwd:wTz7x9b00ImLonRPvGl8CBRb a=candidate:8228103366 1 udp 659136 190.84.118.88 31028 typ host generation 0 a=end-of-candidates a=ssrc:2930644107 cname:If1gLNJdD1HvUPbg a=ssrc:2930644107 msid:8gumHFWDC0sD12iPvVhSeEhUfLdXQBVO a0 a=ssrc:2930644107 mslabel:8gumHFWDC0sD12iPvVhSeEhUfLdXQBVO a=ssrc:2930644107 label:8gumHFWDC0sD12iPvVhSeEhUfLdXQBVOa0 m=video 0 UDP/TLS/RTP/SAVPF 19

3 6

[Freeswitch-dev] mod_callcenter - the configuration property "max-wait-time-with-no-agent" doesn't work
by Alexander Haugg 26 May '20

26 May '20

Hi, The properties "max-wait-time" and "max-wait-time-with-no-agent" have no effect. If the delay is reached, I get the correct debug logs but without an effect. CLI output for the "max-wait-time-with-no-agent" time reached (every 500ms): 2020-04-25 16:29:40.907298 [DEBUG] mod_callcenter.c:2818 Member 170 <+4989840798170> in queue 'myQueue' reached max wait of 60 sec. with no agent plus join grace period of 5 sec. Is it possible, we need the following condition in the 'cc_member_thread_run' function in the mod_callcenter.cs if (switch_channel_test_flag(channel, CF_BREAK)) { switch_channel_clear_flag(channel, CF_BREAK); break; } At the moment, der CF_BREAK will set, but not tested. my config is: <queue name="myQueue"> <param name="strategy" value="agent-with-least-talk-time" /> <param name="max-wait-time" value="300" /> <param name="max-wait-time-with-no-agent" value="60" /> <param name="max-wait-time-with-no-agent-time-reached" value="5" /> <param name="tier-rule-wait-second" value="300" /> <param name="discard-abandoned-after" value="60" /> <param name="announce-frequency" value="0" /> <param name="announce-sound" value="" /> <param name="moh-sound" value="local_stream://moh" /> <param name="time-base-score" value="system" /> <param name="tier-rules-apply" value="false" /> <param name="tier-rule-wait-multiply-level" value="true" /> <param name="tier-rule-no-agent-no-wait" value="false" /> <param name="abandoned-resume-allowed" value="false" /> </queue> If I'm right, I'll open a Jira ticket and add a possible solution. Thanks a lot, Alex

4 4