- FreeSWITCH-users - FreeSWITCH Mailing Lists

Integration with Vocality
by nordin mohamed 19 Apr '13

19 Apr '13

Hi all, Actually I'm quite new with Freeswitch. Currently I'm trying to create a Comm Server that able to provide a conference to voip phone and radio. I'm using Basics Radio Relay(Vocality) as the radio repeater. Basics Radio Relay is using the silent suppression frame as marker to keying the PTT to the radio. Asterisk currently not able to support silent suppression. I thought of using Freeswitch as I know it support for silent suppression. Is there anybody have experience of integration freeswitch and Basic Radio Relay. thank you -nordin mohamed

1 0

Do you use Adhearsion? If so, how?
by Ben Langfeld 19 Apr '13

19 Apr '13

Adhearsion got FreeSWITCH support last year, and it's been awesome since; we've been doing a lot more work with FreeSWITCH and several people have switched projects from Asterisk to FreeSWITCH as a result. Now we'd like to ask a favour of anyone who has used Adhearsion from the FreeSWITCH community. We'd like your feedback in order to help set our course for the future. Only 10 minutes of your time could help the project immeasurably, so please do complete our survey about usage patterns here: https://www.surveymonkey.com/s/53RGSY8 Thanks in advance, Ben Langfeld Adhearsion Foundation

3 2

OPUS in FreeSWITCH
by thomas peterseil 18 Apr '13

18 Apr '13

hello, i just installed the actual version of freeswitch and now i wanted to make opus working. i added and activated the mod_opus module and now i wanted to ask, what else i have to do to make opus work with my freeswitch? i tried to add opus in the vars.xml file, but it didn´t help. what´s the exact syntax i have to use to enable opus in the vars.xml file? are there some other changes i have to do to make it working? thank you very much for your help! best, thomas

2 1

Video call failing between X-Lite softphones
by Navnath Sonavne 18 Apr '13

18 Apr '13

Hi All, I have setup freeswitch to make call but I am only able to make audio call. When I make video call from extension 1100 to 1101(default context) ,at 1100 end it shows sending your video but at 1101 end it does not show any video. In X-Lite phone settings from preferences i have excluded H.263-1998 v-codec and enabled only H.263 v-codec. My vars.xml file contains following codecs : <X-PRE-PROCESS cmd="set" data="global_codec_prefs=G722,PCMU,PCMA,GSM, H263"/> <X-PRE-PROCESS cmd="set" data="outbound_codec_prefs=G722,PCMU,PCMA,GSM,H263"/> I am attaching my 1100.xml and 1101.xml files. Help me out its really urgent for me. Thanks in advance. Regards, Navnath.

2 1

Sangoma Unknown Event Code(5) Invalid PCB state(265)
by Dmitriy Shumaev 18 Apr '13

18 Apr '13

Core 2 Duo E8400 @3.00Ghz 2GB RAM Sangoma A101 Git-1.7.11-preview20120710 FreeSWITCH Version 1.5.1b+git~20130417T225111Z~54d47599e9 wanpipe_6_0_46_0 libsng_isdn-7.6.2 mod_freetdm is loaded successfully (look at full log forwards). But as a reaction on incoming calls FS console shows the next warning message: > 2013-04-18 15:43:33.046875 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:862 [SNGISDN Q931] s1: Internal: Unknown Event Code(5): Invalid PCB state(265). Although the analyzer (linkbit) shows transmission of SETUP, RR, RR, 10sec delay, SETUP, RR, RR from PBX to FS(sangoma). What it could be? Grateful for any answers . Full log: freeswitch@telegraf-4a8f3c> load mod_freetdm 2013-04-18 15:03:35.765625 [INFO] mod_enum.c:872 ENUM Reloaded 2013-04-18 15:03:35.765625 [INFO] switch_time.c:1173 Timezone reloaded 530 definitions 2013-04-18 15:03:35.796875 [NOTICE] ftdm_sched.c:185 Launching main schedule thread 2013-04-18 15:03:35.796875 [NOTICE] ftdm_io.c:6330 Modules configured: 1 2013-04-18 15:03:35.812500 [INFO] ftdm_io.c:5499 Loading IO from C:/FS_GIT/Win32/Release/mod\ftmod_wanpipe.dll [wanpipe] 2013-04-18 15:03:35.812500 [ERR] ftdm_io.c:5445 Cannot open wanpipe.conf 2013-04-18 15:03:35.812500 [INFO] ftdm_io.c:860 Auto-loaded I/O module 'wanpipe' 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c1][1:1] Configured wanpipe device FD: 3620, DTMF: software, HW EC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c2][1:2] Configured wanpipe device FD: 4936, DTMF: software, HW EC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c3][1:3] Configured wanpipe device FD: 4948, DTMF: software, HW EC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c4][1:4] Configured wanpipe device FD: 4956, DTMF: software, HW EC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c5][1:5] Configured wanpipe device FD: 4964, DTMF: software, HW EC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c6][1:6] Configured wanpipe device FD: 4972, DTMF: software, HW EC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c7][1:7] Configured wanpipe device FD: 4980, DTMF: software, HW EC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c8][1:8] Configured wanpipe device FD: 4988, DTMF: software, HW EC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c9][1:9] Configured wanpipe device FD: 4996, DTMF: software, HW EC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c10][1:10] Configured wanpipe device FD: 5004, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c11][1:11] Configured wanpipe device FD: 5012, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c12][1:12] Configured wanpipe device FD: 5020, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c13][1:13] Configured wanpipe device FD: 5028, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c14][1:14] Configured wanpipe device FD: 5036, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c15][1:15] Configured wanpipe device FD: 5044, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c16][1:17] Configured wanpipe device FD: 5052, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c17][1:18] Configured wanpipe device FD: 5060, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c18][1:19] Configured wanpipe device FD: 5068, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c19][1:20] Configured wanpipe device FD: 5076, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c20][1:21] Configured wanpipe device FD: 5084, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c21][1:22] Configured wanpipe device FD: 5092, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c22][1:23] Configured wanpipe device FD: 5100, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c23][1:24] Configured wanpipe device FD: 5108, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c24][1:25] Configured wanpipe device FD: 5116, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c25][1:26] Configured wanpipe device FD: 5124, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c26][1:27] Configured wanpipe device FD: 5132, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c27][1:28] Configured wanpipe device FD: 5140, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c28][1:29] Configured wanpipe device FD: 5148, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c29][1:30] Configured wanpipe device FD: 5156, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c30][1:31] Configured wanpipe device FD: 5164, DTMF: software, HWEC: unavailable, HWEC_IDLE: enabled 2013-04-18 15:03:35.812500 [INFO] ftmod_wanpipe.c:420 [s1c31][1:16] Configured wanpipe device FD: 5168, DTMF: none, HWEC : none, HWEC_IDLE: none 2013-04-18 15:03:35.843750 [INFO] ftdm_io.c:5421 Configured 31 channel(s) 2013-04-18 15:03:35.937500 [INFO] ftdm_io.c:5499 Loading IO from C:/FS_GIT/Win32/Release/mod\ftmod_sangoma_isdn.dll [san goma_isdn] 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn.c:1338 Loading ftmod_sangoma_isdn... 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1102 sng_isdn-> =========================================== = Sangoma FreeTDM ISDN Library = = Version:7.6.2 = =========================================== 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully registered Stack Manager 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully started a task for Stack Ma nager 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully attached Stack Manager to i t's task 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully registered Call Control 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully started a task for Call Con trol 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully attached Call Control to it 's task 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully registered Q.930/Q.931 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully started a task for Q.930/Q. 931 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully attached Q.930/Q.931 to it' s task 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully registered LAPD 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully started a task for LAPD 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully attached LAPD to it's task 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully registered Physical Layer 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully started a task for Physical Layer 2013-04-18 15:03:35.937500 [INFO] ftmod_sangoma_isdn_stack_rcv.c:1098 sng_isdn->Successfully attached Physical Layer to it's task 2013-04-18 15:03:36.437500 [INFO] ftmod_sangoma_isdn_stack_cfg.c:89 General stack configuration done 2013-04-18 15:03:36.437500 [INFO] ftdm_io.c:5511 Loading SIG from C:/FS_GIT/Win32/Release/mod\ftmod_sangoma_isdn.dll 2013-04-18 15:03:36.437500 [INFO] ftdm_io.c:5735 auto-loaded 'sangoma_isdn' 2013-04-18 15:03:36.437500 [INFO] ftmod_sangoma_isdn.c:1184 Configuring ftmod_sangoma_isdn span = wp1 2013-04-18 15:03:36.453125 [INFO] ftmod_sangoma_isdn_stack_cfg.c:159 wp1:stack configuration done 2013-04-18 15:03:36.453125 [INFO] ftmod_sangoma_isdn.c:1331 Finished configuring ftmod_sangoma_isdn span = wp1 2013-04-18 15:03:36.453125 [INFO] ftmod_sangoma_isdn.c:1089 Starting span wp1:1. 2013-04-18 15:03:37.265625 [INFO] ftmod_sangoma_isdn_stack_cntrl.c:88 wp1:Stack activated 2013-04-18 15:03:37.265625 [INFO] ftmod_sangoma_isdn.c:447 ftmod_sangoma_isdn monitor thread for span=1 started. 2013-04-18 15:03:37.265625 [CONSOLE] switch_loadable_module.c:1350 Successfully Loaded [mod_freetdm] 2013-04-18 15:03:37.265625 [INFO] ftmod_sangoma_isdn_stack_rcv.c:825 [SNGISDN Q931] s1: Interface: UP(260): Dchan(285) 2013-04-18 15:03:37.265625 [NOTICE] switch_loadable_module.c:146 Adding Endpoint 'freetdm' 2013-04-18 15:03:37.265625 [NOTICE] switch_loadable_module.c:254 Adding Application 'disable_ec' 2013-04-18 15:03:37.265625 [NOTICE] switch_loadable_module.c:254 Adding Application 'disable_dtmf' 2013-04-18 15:03:37.265625 [NOTICE] switch_loadable_module.c:254 Adding Application 'enable_dtmf' 2013-04-18 15:03:37.265625 [NOTICE] switch_loadable_module.c:298 Adding API Function 'ftdm' 2013-04-18 15:03:37.265625 [NOTICE] switch_loadable_module.c:298 Adding API Function 'ftdm_usage' +OK Reloading XML +OK 2013-04-18 15:03:37.281250 [INFO] ftmod_sangoma_isdn_stack_rcv.c:675 Received RESTART CFM (dChan:1 ces:0 type:0) 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:1 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:2 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:3 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:4 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:5 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:6 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:7 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:8 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:9 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:10 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:11 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:12 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:13 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:14 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:15 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:16 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:17 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:18 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:19 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:20 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:21 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:22 signalling changed to :UP 2013-04-18 15:03:37.281250 [INFO] mod_freetdm.c:2733 1:23 signalling changed to :UP 2013-04-18 15:03:37.296875 [INFO] mod_freetdm.c:2733 1:24 signalling changed to :UP 2013-04-18 15:03:37.296875 [INFO] mod_freetdm.c:2733 1:25 signalling changed to :UP 2013-04-18 15:03:37.296875 [INFO] mod_freetdm.c:2733 1:26 signalling changed to :UP 2013-04-18 15:03:37.296875 [INFO] mod_freetdm.c:2733 1:27 signalling changed to :UP 2013-04-18 15:03:37.296875 [INFO] mod_freetdm.c:2733 1:28 signalling changed to :UP 2013-04-18 15:03:37.296875 [INFO] mod_freetdm.c:2733 1:29 signalling changed to :UP 2013-04-18 15:03:37.296875 [INFO] mod_freetdm.c:2733 1:30 signalling changed to :UP 2013-04-18 15:03:37.296875 [INFO] mod_freetdm.c:2733 1:31 signalling changed to :UP freeswitch@telegraf-4a8f3c> freeswitch@telegraf-4a8f3c> freeswitch@telegraf-4a8f3c> ftdm list +OK span: 1 (wp1) type: Sangoma (ISDN) physical_status: ok signaling_status: UP chan_count: 31 dialplan: XML context: default dial_regex: fail_dial_regex: hold_music: analog_options: none freeswitch@telegraf-4a8f3c> ftdm sangoma_isdn trace q931 wp1 2013-04-18 15:04:38.484375 [INFO] ftmod_sangoma_isdn_stack_cntrl.c:271 s1 Enabling q931 trace Command executed OK freeswitch@telegraf-4a8f3c> ftdm sangoma_isdn trace q921 wp1 2013-04-18 15:04:42.015625 [INFO] ftmod_sangoma_isdn_stack_cntrl.c:261 wp1:Enabling q921 trace Command executed OK freeswitch@telegraf-4a8f3c> 2013-04-18 15:06:44.843750 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:862 [SNGISDN Q931] s1: I nternal: Unknown Event Code(5): Invalid PCB state(265) 2013-04-18 15:06:54.843750 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:862 [SNGISDN Q931] s1: Internal: Unknown Event Code( 5): Invalid PCB state(265) 2013-04-18 15:07:30.375000 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:862 [SNGISDN Q931] s1: Internal: Unknown Event Code( 5): Invalid PCB state(265) 2013-04-18 15:07:40.359375 [WARNING] ftmod_sangoma_isdn_stack_rcv.c:862 [SNGISDN Q931] s1: Internal: Unknown Event Code( 5): Invalid PCB state(265) ... ... ... With best regards, Shumaev DA, KBR Ltd.

2 1

Re-transmit picks up new dns ip address
by Chris Martineau 18 Apr '13

18 Apr '13

Hi, Have a scenario whereby FS sends an invite to another downstream sip server which is late replying and fs then sends a re-transmission, however fs then subsequently gets a reply. Not a major issue as everything should sort itself out. The problem I have is that the downstream server is on a dns-srv roundrobin between 2 servers and the re-transmission is resolving a different server. This seems to be causing the replies that have subsequently come in from the original server to just bounce until they timeout. The re-transmission to the other server seems to carry on fine but sometimes generates a 482 merged call error. The main effect is just messy call stats as I get strange 483 errors generated by fs for some reason internally for the first call and also a normal error or cdr for the re-transmitted part of the call. If I set the downstream server to a fixed ip everything works fine. I assume this should not happen and we should be able to use a dns-svr destination without problems (or not!). I may be just not setting something correctly, any ideas. Many thanks Chris

1 0

execute answer in inbound connection
by Marwan Idriss 18 Apr '13

18 Apr '13

can I execute answer in inbound bound connection ?

2 1

Weird port in "Contact", SIP/2.0 200 OK message
by FSX 18 Apr '13

18 Apr '13

After resolving latest build problems and trying to make a test call to voicemail I see the new problem, that wasn't here in the previous builds. When call is answered by FS, FS sends "SIP/2.0 200 OK message", which now suddenly specified the port #1 instead of its actual port (5080). Here is this part of the message, that FS now sends to SIP client: Contact: <sip:2005@IP.IP.IP.IP:1;transport=udp> As a result, SIP client did not ACK that message and call becomes canceled by FS soon... No audio, of course too. Here is what FS sent in the same configuration using previous (2 weeks ago) build: Contact: <sip:2005@IP.IP.IP.IP:5080;transport=udp> where: 5080 is example of FS port, configured for taking connections form SIP clients. Here is yet another difference in console log that I hope may give a clue why is that now. In the latest build FS prints this line: 2013-04-11 21:10:57.079034 [NOTICE] sofia_media.c:92 Pre-Answer sofia/internal/2005@domain while with previous build (which was working well) the line was: 2013-04-11 21:15:22.361652 [NOTICE] sofia_glue.c:4281 Pre-Answer sofia/internal/2005@domain While the latest build offered a lot of configuration changes comparing to previous (and working) version, I can't find anything related to that strange change... Latest build, used for test (not working) (made 130410): fe4dff7 Previous (and working well) build (made 130326): bb3114e -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Weird-port-in-Contact-SIP-2-0… Sent from the freeswitch-users mailing list archive at Nabble.com.

5 14

mod_fifo: agents are not ringing
by Ashish gautam 18 Apr '13

18 Apr '13

Hi, Caller is played music on hold but is not connected to any of the agents since no agent is ringing. I have sip users registered to FS ( they are online). I have configured a SIP user as a member for the queue. But, when the caller calls in, the agent doesn't ring. Please throw some light. -Ashish

2 13

Strange MANAGER_REQUEST hangups
by Alex Crow 18 Apr '13

18 Apr '13

Hi there, The wiki states that the above hangup cause is used when a call is hung up from the API. However, I've recently been getting some calls being hung up (often, oddly, multiple calls simultaneously - this is all on a system without automated calls) with this reason, eg: freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/02076084900(a)10.10.0.2 [CS_EXCHANGE_MEDIA] [MANAGER_REQUEST] freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/02076087470(a)10.10.0.2 [CS_EXCHANGE_MEDIA] [MANAGER_REQUEST] freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/2076087440(a)10.10.0.2 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-16-13-16-57.1:2013-04-16 13:02:42.455796 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc/02076087440(a)10.10.0.2 [CS_EXCHANGE_MEDIA] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441768351327(a)88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441502563921(a)88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441325460860(a)88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+447870616904(a)88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] freeswitch.log.2013-04-17-09-53-16.1:2013-04-17 09:35:42.115787 [NOTICE] switch_core_session.c:246 Hangup sofia/sbc-ext/+441325385210(a)88.215.61.195 [CS_EXECUTE] [MANAGER_REQUEST] Is there any other reason that could produce this Cause code? I am *definitely* not executing any api commands to hang up channels. Thanks Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856).

2 3