August 2019 - FreeSWITCH-users - FreeSWITCH Mailing Lists

Unable to start the Free switch server
by veeru anji 05 Aug '19

05 Aug '19

Dear Team, I am getting below error message. This is the result when I am trying with Sofia status command freeswitch@CITHYDDKTP-030> Sofia Status Name Type Data State ================================================================================================= external-ipv6 profile sip:mod_sofia@[::1]:5080 RUNNING (0) external profile sip:mod_sofia@183.82.114.188:5080 RUNNING (0) external::example.com gateway sip:joeuser@example.com NOREG ================================================================================================= 2 profiles 0 aliases But below error is coming>>>>>>>>>>>>>> *Error Creating SIP UA for profile: internal-ipv6 (sip:mod_sofia@[::1]:5060;transport=udp,tcp) ATTEMPT 3 (RETRY IN 5 SEC)2019-08-05 16:20:23.012205 [ERR] sofia.c:3238 Error Creating SIP UA for profile: internal-ipv6 (sip:mod_sofia@[::1]:5060;transport=udp,tcp)The likely causes for this are:1) Another application is already listening on the specified address.2) The IP the profile is attempting to bind to is not local to this system.*

1 0

Trying to install Docker Container FS
by Danny Dias 03 Aug '19

03 Aug '19

Hi Community! Having some weird issues following this guide to install my FS Containers: https://hub.docker.com/r/bettervoice/freeswitch-container/ I ran the following command to download and run the image: dadiaspe@srv-lx-containers-fs-01:~$ CID=$(sudo docker run --name freeswitch -p 5060:5060/tcp -p 5060:5060/udp -p 5080:5080/tcp -p 5080:5080/udp -p 8021:8021/tcp -p 7443:7443/tcp -p 60535-65535:60535-65535/udp -v /home/debian/freeswitch/conf:/usr/local/freeswitch/conf bettervoice/freeswitch-container:1.6.6) It did several Pulls and Downloads, and returned the following message at the end: Digest: sha256:e0db31cd71a7c8ef63be9b20c438bc94f29b73dc147b294a9e1d2b6ce17b2a01 Status: Downloaded newer image for bettervoice/freeswitch-container:1.6.6 . . freeswitch is not configured so not starting. Please review /usr/local/doc/freeswitch/README.Debian *tail: unrecognized file system type 0x794c7630 for '/usr/local/freeswitch/log/freeswitch.log'. please report this to bug-coreutils(a)gnu.org <bug-coreutils(a)gnu.org>. reverting to polling* But the container seems to be running cause i can connect, and "docker ps -a" reports the container UP: dadiaspe@srv-lx-containers-fs-01:~$ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d70484c9f2cb bettervoice/freeswitch-container:1.6.6 "/bin/sh -c 'service…" About an hour ago Up 56 minutes 0.0.0.0:5060->5060/tcp, 0.0.0.0:5060->5060/udp, 0.0.0.0:5080->5080/tcp, 0.0.0.0:7443->7443/tcp, 0.0.0.0:5080->5080/udp, 0.0.0.0:8021->8021/tcp, 0.0.0.0:60535-65535->60535-65535/udp, 5066/tcp freeswitch dadiaspe@srv-lx-containers-fs-01:~$ docker exec -it freeswitch /bin/bash root@d70484c9f2cb:/usr/src/freeswitch# FS appears to be running: root@d70484c9f2cb:/usr/src/freeswitch# ps -aux | grep free root 1 0.0 0.0 4444 620 ? Ss 21:07 0:00 /bin/sh -c service snmpd start && service freeswitch start && tail -f /usr/local/freeswitch/log/freeswitch.log root 21 0.0 0.0 4380 800 ? S 21:07 0:00 tail -f /usr/local/freeswitch/log/freeswitch.log root 71 0.0 0.0 8864 884 pts/0 S+ 22:07 0:00 grep --color=auto free But can't connect to fs_cli: root@d70484c9f2cb:/usr/src/freeswitch# /usr/local/freeswitch/bin/fs_cli *[ERROR] fs_cli.c:1659 main() Error Connecting [Socket Connection Error]* Am i doing something wrong with the container? I'm planning to run around 4 FS containers in this Host...any ideas/recommendations highly appreciated! Thank u

2 1

dialplan continues with bypass_media
by Keith 03 Aug '19

03 Aug '19

I have a mod_python dialplan and have been experimenting with taking FreeSwitch out of the media path when the call answers. It's working great now, and scheduled playback, hangup works brilliantly! However, I noticed that when I set channel variable bypass_media or bypass_media_after_bridge then the dialplan continues as soon as the media is bypassed. I am doing some things in the dialplan after the bridge, like playing audio depending on the hang-up cause, but also some logging of call timings after the bridge. see: https://github.com/Rhizomatica/rccn/blob/master/rccn/context.py#L258 I was surprised to see that code running when I set bypass_media_after_bridge on the channel, but maybe my logic is wrong here, and I should just return after session.execute('bridge') when originate_disposition is SUCCESS and handle the logging in the hangup hook? All the same, I was wondering if there was any way to not have the bridge return after media is bypassed? I've scoured the docs and had a look through the source code and I think the answer is no, but I thought I'd ask. I'm also interested as to the logic of why then the bridge function does not return on SUCCESS if one is not bypassing media. Thanks! Keith.

1 0

Excessive logging?
by Allan Kristensen 01 Aug '19

01 Aug '19

Hello, I'm using the master branch to test some things and I've noticed that there is a lot of these: 2019-08-01 11:50:07.238469 [NOTICE] switch_rtp.c:2191 Sending RTCP SR (ssrc=3712758684) 2019-08-01 11:50:08.258456 [NOTICE] switch_rtp.c:2191 Sending RTCP SR (ssrc=3712758684) 2019-08-01 11:50:09.278517 [NOTICE] switch_rtp.c:2191 Sending RTCP SR (ssrc=3712758684) 2019-08-01 11:50:10.298459 [NOTICE] switch_rtp.c:2191 Sending RTCP SR (ssrc=3712758684) 2019-08-01 11:50:10.518468 [NOTICE] switch_rtp.c:2191 Sending RTCP SR (ssrc=156472476) 2019-08-01 11:50:11.318554 [NOTICE] switch_rtp.c:2191 Sending RTCP SR (ssrc=3712758684) 2019-08-01 11:50:12.338457 [NOTICE] switch_rtp.c:2191 Sending RTCP SR (ssrc=3712758684) 2019-08-01 11:50:13.358469 [NOTICE] switch_rtp.c:2191 Sending RTCP SR (ssrc=3712758684) 2019-08-01 11:50:14.378473 [NOTICE] switch_rtp.c:2191 Sending RTCP SR (ssrc=3712758684) I can see the log level was changed from SWITCH_LOG_DEBUG1 to SWITCH_LOG_NOTICE in commit https://freeswitch.org/stash/projects/FS/repos/freeswitch/commits/7906a2054… is this on purpose? Thank you... /Allan

2 1