January 2011 - FreeSWITCH-users - FreeSWITCH Mailing Lists

Question About Conferencing Capabilities
by siobhan.pluggedin＠gmail.com 04 Jan '11

04 Jan '11

My company is building a VOIP application, and initially were just using a barebones OpenSIPS implementation to host one-on-one calls; however, we want to expand the functionality to conferencing (which, of course, OpenSIPS doesn't handle) and was looking into Freeswitch (the other option being Asterisk). I've been poring through the docs, and have even set up a test server myself, but there are some very specific things we are looking for that I can't figure out if Freeswitch can do or not. We want to be able to do the following: - Create dynamic, on-the-fly conferences that can remain active even when initiating user leaves - Within a conference, give users the ability to mute and/or deaf individual users (which I know can already be done with the "relate" command) - Give users the ability to enter a "whisper" mode with another user - where they are holding a private conversation that can only be heard by the two of them - Allow users to be in two conferences at once; the user would most likely have one muted at any given time so as to hear the other one, but we want them to be able to switch back and forth easily Could anyone advise me on whether Freeswitch can accomplish these needs, or perhaps what it might take to do so? We are not averse to doing some customization if we can find the people who know how to make it happen! Thanks, Siobhan Hamilton

1 0

Re: [Freeswitch-users] mode_nibblebill and mod_conference
by Madovsky 04 Jan '11

04 Jan '11

in mod_nibblebill wiki page a.. Q: Can you bill based on a multi-call B-Leg, where you have, say a conference call with multiple people on it? a.. Yes, see answer above re: B-Leg and not A-Leg. but if I have this in my dialplan <extension name="conference"> <condition field="destination_number" expression="^conference$"> <action application="export" data="nolocal:nibble_account=${dest_nibble_account}"/> <action application="export" data="nolocal:nibble_rate=0.03"/> <action application="sleep" data="3000"/> <action application="answer"/>  <action application="conference" data="${dest_nibble_account}-$${domain}@default+${dest_conf_pin}"/> </condition> </extension> it doesn't work ----- Original Message ----- From: Madovsky To: freeswitch-users(a)lists.freeswitch.org Sent: Monday, January 03, 2011 2:21 PM Subject: mode_nibblebill and mod_conference Is nibblebill works with conference ? I tried to set nibble_account and nibble_rate without success Thanks

2 4

libss7 * Sangoma
by Anita Hall 04 Jan '11

04 Jan '11

Hi This question pertains libss7 with Sangoma A108 card on Asterisk. It does not concern freeswitch but I suppose Sangoma folks frequent this list more :) I am unable to make libss7 work with Sangoma. Here are the details. Could you please provide me some pointers ? Thanks, Anita. debian:~# uname -a Linux debian 2.6.26-2-686 #1 SMP Thu Nov 25 01:53:57 UTC 2010 i686 GNU/Linux debian:~# dahdi_hardware pci:0000:05:04.0 wanpipe- 1923:0100 Sangoma Technologies Corp. A104d QUAD T1/E1 AFT card pci:0000:07:04.0 wanpipe- 1923:0100 Sangoma Technologies Corp. A104d QUAD T1/E1 AFT card debian:~# cat /etc/dahdi/system.conf #autogenerated by /usr/sbin/wancfg_dahdi do not hand edit #autogenrated on 2011-01-03 #Dahdi Channels Configurations #For detailed Dahdi options, view /etc/dahdi/system.conf.bak loadzone=us defaultzone=us #Sangoma A108 port 1 [slot:4 bus:5 span:1] <wanpipe1> span=1,1,0,ccs,hdb3,crc4 bchan=1-15,17-31 echocanceller=mg2,1-15,17-31 mtp2=16 #Sangoma A108 port 2 [slot:4 bus:5 span:2] <wanpipe2> span=2,1,0,ccs,hdb3,crc4 bchan=32-46,48-62 echocanceller=mg2,32-46,48-62 mtp2=47 debian:~# cat /etc/wanpipe/wanpipe1.conf #============================= =================== # WANPIPE1 Configuration File #================================================ # # Date: Wed Dec 6 20:29:03 UTC 2006 # # Note: This file was generated automatically # by /usr/local/sbin/setup-sangoma program. # # If you want to edit this file, it is # recommended that you use wancfg program # to do so. #================================================ # Sangoma Technologies Inc. #================================================ [devices] wanpipe1 = WAN_AFT_TE1, Comment [interfaces] w1g1 = wanpipe1, , TDM_VOICE, Comment [wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 4 PCIBUS = 5 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME = NCRC4 FE_LINE = 1 TE_CLOCK = NORMAL TE_REF_CLOCK = 0 TE_SIG_MODE = CCS TE_HIGHIMPEDANCE = NO LBO = 120OH FE_TXTRISTATE = NO MTU = 1500 UDPPORT = 9000 TTL = 255 IGNORE_FRONT_END = NO TDMV_SPAN = 1 TDMV_DCHAN = 16 TDMV_HW_DTMF = NO TDMV_HW_FAX_DETECT = NO [w1g1] ACTIVE_CH = ALL TDMV_HWEC = NO debian:~# cat /etc/wanpipe/wanpipe2.conf #================================================ # WANPIPE1 Configuration File #================================================ # # Date: Wed Dec 6 20:29:03 UTC 2006 # # Note: This file was generated automatically # by /usr/local/sbin/setup-sangoma program. # # If you want to edit this file, it is # recommended that you use wancfg program # to do so. #================================================ # Sangoma Technologies Inc. #================================================ [devices] wanpipe2 = WAN_AFT_TE1, Comment [interfaces] w2g1 = wanpipe2, , TDM_VOICE, Comment [wanpipe2] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 4 PCIBUS = 5 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME = NCRC4 FE_LINE = 2 TE_CLOCK = NORMAL TE_REF_CLOCK = 0 TE_SIG_MODE = CCS TE_HIGHIMPEDANCE = NO LBO = 120OH FE_TXTRISTATE = NO MTU = 1500 UDPPORT = 9000 TTL = 255 IGNORE_FRONT_END = NO TDMV_SPAN = 2 TDMV_DCHAN = 16 TDMV_HW_DTMF = NO TDMV_HW_FAX_DETECT = NO [w2g1] ACTIVE_CH = ALL TDMV_HWEC = NO debian:~# cat /etc/asterisk/chan_dahdi.conf ;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit ;autogenrated on 2011-01-03 ;Dahdi Channels Configurations ;For detailed Dahdi options, view /etc/asterisk/chan_dahdi.conf.bak [trunkgroups] [channels] context=default usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes relaxdtmf=yes rxgain=0.0 txgain=0.0 group=1 callgroup=1 pickupgroup=1 immediate=no ;Sangoma A108 port 1 [slot:4 bus:5 span:1] <wanpipe1> switchtype=euroisdn context=tata group=1 echocancel=yes signaling=ss7 ;this is ss7 signaling ss7type=itu ;using the ITU variant ss7_called_nai=dynamic ;NAI for outgoing calls ss7_calling_nai=dynamic ;NAI for incoming calls ss7_internationalprefix=00 ;international prefix value for incoming calls ss7_nationalprefix=0 ;national prefix value for incoming calls ss7_subscriberprefix= ;subscriber prefix value for incoming calls ss7_unknownprefix= ;unknown prefix value for incoming calls ss7_explictacm=yes ;ACM is send as soon as call enters the dial plan...may not accepted yet though linkset=1 ;arbitrary name for this set of channels pointcode=13323 ;the point code for this system...aka SPC adjpointcode=12650 ;the point code for the system that we are signaling to... aka APC defaultdpc=12650 ;the point code for the system that the CICs will be negotiated with...aka DPC networkindicator=international ;NI value for MTP3 cicbeginswith=1 ;the starting value of the CICs channel =>1-15 cicbeginswith=17 ;the starting value of the CICs channel =>17-31 ;the channels that are CICs sigchan=16 ;the signaling channel ;Sangoma A108 port 2 [slot:4 bus:5 span:2] <wanpipe2> switchtype=euroisdn context=tata group=1 echocancel=yes cicbeginswith=32 ;the starting value of the CICs channel =>32-46 cicbeginswith=48 ;the starting value of the CICs channel =>48-62 ;the channels that are CICs sigchan=47 ;the signaling channel debian:~# ifconfig w1g1 w1g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:772814 errors:0 dropped:0 overruns:0 frame:0 TX packets:772814 errors:0 dropped:0 overruns:3 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff debian:~# ifconfig w1g1 w1g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:774782 errors:0 dropped:0 overruns:0 frame:0 TX packets:774782 errors:0 dropped:0 overruns:3 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff debian:~# ifconfig w1g1 w1g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:775351 errors:0 dropped:0 overruns:0 frame:0 TX packets:775351 errors:0 dropped:0 overruns:3 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff debian:~# ifconfig w1g1 w1g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:775919 errors:0 dropped:0 overruns:0 frame:0 TX packets:775919 errors:0 dropped:0 overruns:3 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff debian:~# ifconfig w1g1 w1g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:776478 errors:0 dropped:0 overruns:0 frame:0 TX packets:776478 errors:0 dropped:0 overruns:3 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff debian:~# ifconfig w1g1 w1g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:777079 errors:0 dropped:0 overruns:0 frame:0 TX packets:777079 errors:0 dropped:0 overruns:3 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff debian:~# ifconfig w1g1 w1g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:778134 errors:0 dropped:0 overruns:0 frame:0 TX packets:778134 errors:0 dropped:0 overruns:3 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff debian:~# ifconfig w2g1 w2g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:792251 errors:0 dropped:0 overruns:0 frame:0 TX packets:792251 errors:0 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff debian:~# ifconfig w2g1 w2g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:792715 errors:0 dropped:0 overruns:0 frame:0 TX packets:792715 errors:0 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff debian:~# ifconfig w2g1 w2g1 Link encap:Point-to-Point Protocol UP POINTOPOINT RUNNING NOARP MTU:8 Metric:1 RX packets:793219 errors:0 dropped:0 overruns:0 frame:0 TX packets:793219 errors:0 dropped:0 overruns:1 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 Memory:f8d00000-f8d01fff wanpipemon -i w2g1 -c Ta ***** w2g1: E1 Alarms (Framer) ***** ALOS: OFF | LOS: OFF RED: OFF | AIS: OFF LOF: OFF | RAI: OFF ***** w2g1: E1 Alarms (LIU) ***** Short Circuit: OFF Open Circuit: OFF Loss of Signal: OFF ***** w2g1: E1 Performance Monitoring Counters ***** Line Code Violation : 0 Far End Block Errors : 0 CRC4 Errors : 0 FAS Errors : 0 Rx Level : > -2.5db debian:~# wanpipemon -i w1g1 -c Ta ***** w1g1: E1 Alarms (Framer) ***** ALOS: OFF | LOS: OFF RED: OFF | AIS: OFF LOF: OFF | RAI: OFF ***** w1g1: E1 Alarms (LIU) ***** Short Circuit: OFF Open Circuit: OFF Loss of Signal: OFF ***** w1g1: E1 Performance Monitoring Counters ***** Line Code Violation : 371 Far End Block Errors : 0 CRC4 Errors : 0 FAS Errors : 0 Rx Level : > -2.5db Jan 3 20:33:34 debian kernel: [55441.172179] wanpipe1: Shutting Down! Jan 3 20:33:34 debian kernel: [55441.172179] wanpipe1: E1 Front End unconfigation! Jan 3 20:33:34 debian kernel: [55441.172179] wanpipe1: Unregister Wanpipe device from Zaptel! Jan 3 20:33:34 debian kernel: [55441.178246] wanpipe1: unregistering 'w1g1' Jan 3 20:33:34 debian kernel: [55441.248278] wanpipe1: TASKQ Not Running Jan 3 20:33:34 debian kernel: [55441.248281] wanpipe1: E1 Front End unconfigation! Jan 3 20:33:34 debian kernel: [55441.248314] wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down) Jan 3 20:33:34 debian kernel: [55441.248335] wanpipe1: E1 Front End unconfigation! Jan 3 20:33:34 debian kernel: [55441.248373] wanpipe1: AFT communications disabled! (Dev Cnt: 1 Cause: Device Down) Jan 3 20:33:34 debian kernel: [55441.248415] wanpipe1: Global Chip Shutdown Usage=1 Jan 3 20:33:34 debian kernel: [55441.248419] wanpipe1: Global E1 Front End unconfigation! Jan 3 20:33:34 debian kernel: [55441.250485] wanpipe1: Master shutting down Jan 3 20:33:34 debian kernel: [55441.444571] wanpipe1: Starting WAN Setup Jan 3 20:33:34 debian kernel: [55441.444575] wanpipe1: Locating: A101/1D/A102/2D/4/4D/8 card, CPU A, PciSlot=4, PciBus=5 Jan 3 20:33:34 debian kernel: [55441.444579] wanpipe1: Found: A101/1D/A102/2D/4/4D/8 card, CPU A, PciSlot=4, PciBus=5, Port=0 Jan 3 20:33:34 debian kernel: [55441.444599] wanpipe1: AFT PCI memory at 0xD3200000 Jan 3 20:33:34 debian kernel: [55441.444600] wanpipe1: IRQ 16 allocated to the AFT PCI card Jan 3 20:33:34 debian kernel: [55441.444608] wanpipe1: Starting AFT 2/4/8 Hardware Init. Jan 3 20:33:34 debian kernel: [55441.444614] wanpipe1: Enabling front end link monitor Jan 3 20:33:34 debian kernel: [55441.444616] wanpipe1: Global Chip Configuration: used=1 Jan 3 20:33:34 debian kernel: [55441.448455] wanpipe1: Global E1 Front End configuration Jan 3 20:33:34 debian kernel: [55441.448455] wanpipe1: AFT Data Mux Bit Map: 0x01234567 Jan 3 20:33:34 debian kernel: [55441.448455] wanpipe1: Defaulting E1 Rx Sens. Gain= 43 db Jan 3 20:33:34 debian kernel: [55441.448455] wanpipe1: Configuring DS DS26528 E1 FE Jan 3 20:33:34 debian kernel: [55441.448455] wanpipe1: Port 1,HDB3,non-CRC4,120OH Jan 3 20:33:34 debian kernel: [55441.448455] wanpipe1: Clk Normal:0, Channels: FFFFFFFF Jan 3 20:33:34 debian kernel: [55441.448455] wanpipe1: Sig Mode CCS Jan 3 20:33:34 debian kernel: [55441.456490] wanpipe1: Rx Sensitivity Gain 43dB (default). Jan 3 20:33:34 debian kernel: [55441.457242] wanpipe1: Front end successful Jan 3 20:33:34 debian kernel: [55441.457469] wanpipe1: Front End Interface Ready 0x40000000 Jan 3 20:33:34 debian kernel: [55441.457473] wanpipe1: WARNING: No Echo Canceller channels are available! Jan 3 20:33:34 debian kernel: [55441.457494] wanpipe1: Configuring Device :wanpipe1 FrmVr=39 Jan 3 20:33:34 debian kernel: [55441.457495] wanpipe1: Global MTU = 1500 Jan 3 20:33:34 debian kernel: [55441.457496] wanpipe1: Global MRU = 1500 Jan 3 20:33:34 debian kernel: [55441.457497] wanpipe1: Data Mux Map = 0x01234567 Jan 3 20:33:34 debian kernel: [55441.457498] wanpipe1: Rx CRC Bytes = 0 Jan 3 20:33:34 debian kernel: [55441.457499] wanpipe1: Global TDM Int = Enabled Jan 3 20:33:34 debian kernel: [55441.457500] wanpipe1: Global TDM Ring = Enabled Jan 3 20:33:34 debian kernel: [55441.457501] wanpipe1: TDMV HW DTMF/FAX = Disabled/Disabled(0) Jan 3 20:33:34 debian kernel: [55441.457502] wanpipe1: TDMV Span = 1 : Enabled Jan 3 20:33:34 debian kernel: [55441.457503] wanpipe1: TDMV Dummy = Disabled Jan 3 20:33:34 debian kernel: [55441.457505] wanpipe1: RTP TAP = Disabled Jan 3 20:33:34 debian kernel: [55441.457540] wanpipe1: Configuring Interface: w1g1 Jan 3 20:33:34 debian kernel: [55441.457543] wanpipe1:w1g1: Running in TDM Voice Zaptel Mode. Jan 3 20:33:34 debian kernel: [55441.457547] wanpipe1: Fifo Level Map:0x01041040 Jan 3 20:33:34 debian kernel: [55441.457549] wanpipe1: MRU :8 Jan 3 20:33:34 debian kernel: [55441.457550] wanpipe1: MTU :8 Jan 3 20:33:34 debian kernel: [55441.457551] wanpipe1: HDLC Eng :Off (Transparent) | N/A Jan 3 20:33:34 debian kernel: [55441.457553] wanpipe1: Data Mux Ctrl :On Jan 3 20:33:34 debian kernel: [55441.457554] wanpipe1: Active Ch Map :0x00000002 Jan 3 20:33:34 debian kernel: [55441.457555] wanpipe1: First TSlot :1 Jan 3 20:33:34 debian kernel: [55441.457568] wanpipe1: DMA/Len/Chain/EC :4/1024/Off/Off Jan 3 20:33:34 debian kernel: [55441.457575] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457581] wanpipe1: Active Ch Map :0x00000004 Jan 3 20:33:34 debian kernel: [55441.457582] wanpipe1: First TSlot :2 Jan 3 20:33:34 debian kernel: [55441.457597] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457602] wanpipe1: Active Ch Map :0x00000008 Jan 3 20:33:34 debian kernel: [55441.457603] wanpipe1: First TSlot :3 Jan 3 20:33:34 debian kernel: [55441.457618] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457623] wanpipe1: Active Ch Map :0x00000010 Jan 3 20:33:34 debian kernel: [55441.457624] wanpipe1: First TSlot :4 Jan 3 20:33:34 debian kernel: [55441.457637] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457643] wanpipe1: Active Ch Map :0x00000020 Jan 3 20:33:34 debian kernel: [55441.457644] wanpipe1: First TSlot :5 Jan 3 20:33:34 debian kernel: [55441.457657] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457663] wanpipe1: Active Ch Map :0x00000040 Jan 3 20:33:34 debian kernel: [55441.457664] wanpipe1: First TSlot :6 Jan 3 20:33:34 debian kernel: [55441.457678] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457684] wanpipe1: Active Ch Map :0x00000080 Jan 3 20:33:34 debian kernel: [55441.457685] wanpipe1: First TSlot :7 Jan 3 20:33:34 debian kernel: [55441.457698] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457705] wanpipe1: Active Ch Map :0x00000100 Jan 3 20:33:34 debian kernel: [55441.457706] wanpipe1: First TSlot :8 Jan 3 20:33:34 debian kernel: [55441.457719] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457725] wanpipe1: Active Ch Map :0x00000200 Jan 3 20:33:34 debian kernel: [55441.457726] wanpipe1: First TSlot :9 Jan 3 20:33:34 debian kernel: [55441.457740] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457746] wanpipe1: Active Ch Map :0x00000400 Jan 3 20:33:34 debian kernel: [55441.457747] wanpipe1: First TSlot :10 Jan 3 20:33:34 debian kernel: [55441.457760] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457765] wanpipe1: Active Ch Map :0x00000800 Jan 3 20:33:34 debian kernel: [55441.457766] wanpipe1: First TSlot :11 Jan 3 20:33:34 debian kernel: [55441.457781] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457786] wanpipe1: Active Ch Map :0x00001000 Jan 3 20:33:34 debian kernel: [55441.457787] wanpipe1: First TSlot :12 Jan 3 20:33:34 debian kernel: [55441.457801] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457807] wanpipe1: Active Ch Map :0x00002000 Jan 3 20:33:34 debian kernel: [55441.457808] wanpipe1: First TSlot :13 Jan 3 20:33:34 debian kernel: [55441.457822] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457828] wanpipe1: Active Ch Map :0x00004000 Jan 3 20:33:34 debian kernel: [55441.457829] wanpipe1: First TSlot :14 Jan 3 20:33:34 debian kernel: [55441.457842] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457848] wanpipe1: Active Ch Map :0x00008000 Jan 3 20:33:34 debian kernel: [55441.457849] wanpipe1: First TSlot :15 Jan 3 20:33:34 debian kernel: [55441.457862] wanpipe1: Configuring Interface: w1g1 Jan 3 20:33:34 debian kernel: [55441.457864] wanpipe1:w1g1: Running in TDM DCHAN Voice Zaptel Mode. Jan 3 20:33:34 debian kernel: [55441.457866] wanpipe1: MRU :1500 Jan 3 20:33:34 debian kernel: [55441.457867] wanpipe1: MTU :1500 Jan 3 20:33:34 debian kernel: [55441.457868] wanpipe1: HDLC Eng :On | N/A Jan 3 20:33:34 debian kernel: [55441.457869] wanpipe1: Data Mux Ctrl :Off Jan 3 20:33:34 debian kernel: [55441.457870] wanpipe1: Active Ch Map :0x00010000 Jan 3 20:33:34 debian kernel: [55441.457871] wanpipe1: First TSlot :16 Jan 3 20:33:34 debian kernel: [55441.457881] wanpipe1: DMA/Len/Chain/EC :65/4096/On/Off Jan 3 20:33:34 debian kernel: [55441.457905] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457910] wanpipe1: Active Ch Map :0x00020000 Jan 3 20:33:34 debian kernel: [55441.457911] wanpipe1: First TSlot :17 Jan 3 20:33:34 debian kernel: [55441.457925] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457931] wanpipe1: Active Ch Map :0x00040000 Jan 3 20:33:34 debian kernel: [55441.457932] wanpipe1: First TSlot :18 Jan 3 20:33:34 debian kernel: [55441.457945] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457951] wanpipe1: Active Ch Map :0x00080000 Jan 3 20:33:34 debian kernel: [55441.457952] wanpipe1: First TSlot :19 Jan 3 20:33:34 debian kernel: [55441.457967] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457973] wanpipe1: Active Ch Map :0x00100000 Jan 3 20:33:34 debian kernel: [55441.457974] wanpipe1: First TSlot :20 Jan 3 20:33:34 debian kernel: [55441.457987] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.457993] wanpipe1: Active Ch Map :0x00200000 Jan 3 20:33:34 debian kernel: [55441.457994] wanpipe1: First TSlot :21 Jan 3 20:33:34 debian kernel: [55441.458009] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458015] wanpipe1: Active Ch Map :0x00400000 Jan 3 20:33:34 debian kernel: [55441.458016] wanpipe1: First TSlot :22 Jan 3 20:33:34 debian kernel: [55441.458030] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458036] wanpipe1: Active Ch Map :0x00800000 Jan 3 20:33:34 debian kernel: [55441.458037] wanpipe1: First TSlot :23 Jan 3 20:33:34 debian kernel: [55441.458051] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458057] wanpipe1: Active Ch Map :0x01000000 Jan 3 20:33:34 debian kernel: [55441.458058] wanpipe1: First TSlot :24 Jan 3 20:33:34 debian kernel: [55441.458072] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458078] wanpipe1: Active Ch Map :0x02000000 Jan 3 20:33:34 debian kernel: [55441.458079] wanpipe1: First TSlot :25 Jan 3 20:33:34 debian kernel: [55441.458094] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458100] wanpipe1: Active Ch Map :0x04000000 Jan 3 20:33:34 debian kernel: [55441.458101] wanpipe1: First TSlot :26 Jan 3 20:33:34 debian kernel: [55441.458116] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458122] wanpipe1: Active Ch Map :0x08000000 Jan 3 20:33:34 debian kernel: [55441.458123] wanpipe1: First TSlot :27 Jan 3 20:33:34 debian kernel: [55441.458137] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458143] wanpipe1: Active Ch Map :0x10000000 Jan 3 20:33:34 debian kernel: [55441.458144] wanpipe1: First TSlot :28 Jan 3 20:33:34 debian kernel: [55441.458160] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458166] wanpipe1: Active Ch Map :0x20000000 Jan 3 20:33:34 debian kernel: [55441.458167] wanpipe1: First TSlot :29 Jan 3 20:33:34 debian kernel: [55441.458181] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458187] wanpipe1: Active Ch Map :0x40000000 Jan 3 20:33:34 debian kernel: [55441.458188] wanpipe1: First TSlot :30 Jan 3 20:33:34 debian kernel: [55441.458202] wanpipe1: Configuring Interface: w1g1 (log supress) Jan 3 20:33:34 debian kernel: [55441.458205] wanpipe1: Configuring TDMV Master dev w1g1 Jan 3 20:33:34 debian kernel: [55441.458209] wanpipe1: Active Ch Map :0x80000000 Jan 3 20:33:34 debian kernel: [55441.458210] wanpipe1: First TSlot :31 Jan 3 20:33:34 debian kernel: [55441.458226] wanpipe1: Enable Zaptel HW DCHAN interface Jan 3 20:33:34 debian kernel: [55441.458462] wanpipe1: Wanpipe device is registered to Zaptel span # 1! Jan 3 20:33:34 debian kernel: [55441.458760] wanpipe1: TDM Free Run Timing Enabled 1 ms Jan 3 20:33:34 debian kernel: [55441.464708] wanpipe1: Wanpipe Front End Interrupt Restart Timeout Jan 3 20:33:40 debian kernel: [55450.402880] wanpipe1: E1 connected! Jan 3 20:33:40 debian kernel: [55450.407421] wanpipe1: AFT communications enabled! Jan 3 20:33:40 debian kernel: [55450.407421] wanpipe1: AFT Global TDM Intr Jan 3 20:33:40 debian kernel: [55450.409902] wanpipe1: Global TDM Ring Resync Jan 3 20:33:41 debian kernel: [55452.785733] wanpipe1: Enable E1 CCS Signalling mode! debian*CLI> core show version Asterisk 1.6.2.0 built by root @ debian on a i686 running Linux on 2011-01-03 08:57:50 UTC debian*CLI> ss7 show linkset 1 SS7 linkset 1 status: Down debian*CLI> ss7 set debug off linkset 1 Enabled debugging on linkset 1 Len = 4 [ ff ff 01 03 ] FSN: 127 FIB 1 BSN: 127 BIB 1 <[0] LSSU SIOS Link state change: NOTALIGNED -> NOTALIGNED Len = 4 [ ff ff 01 00 ] FSN: 127 FIB 1 BSN: 127 BIB 1 <[0] LSSU SIO Link state change: NOTALIGNED -> ALIGNED Len = 4 [ ff ff 01 02 ] FSN: 127 FIB 1 BSN: 127 BIB 1 >[0] LSSU SIE Link state change: ALIGNED -> IDLE Link state change: IDLE -> NOTALIGNED Len = 4 [ ff ff 01 00 ] FSN: 127 FIB 1 BSN: 127 BIB 1 >[0] LSSU SIO

2 1

calling card app
by Rafqat . 03 Jan '11

03 Jan '11

Hi As stated in some of my previous posts, I am writing a calling card system (not too sure of potential number of concurrent users yet). At the moment I am simply doing everything in a single lua script utilising mod_lcr and mod_nibble. It seems to work ok, but I have not stress tested it yet. I was wondering (at a high level) if this will suffice or should I be offloading operations such as pin validation and credit checking to another server (maybe utilising mod_rad_auth?). Cheers Raf

2 5

Re: [Freeswitch-users] Can't build on Windows 7 64bit C++ Express!?
by Peter Olsson 03 Jan '11

03 Jan '11

Make sure to disable autocrlf in git, then it will work. Also make sure to read all instructions on the wiki. /Peter ----- Reply message ----- Från: "xuyan yang" <xyangni(a)gmail.com> Datum: mån, jan 3, 2011 17:54 Rubrik: [Freeswitch-users] Can't build on Windows 7 64bit C++ Express!? Till: "FreeSWITCH Users Help" <freeswitch-users(a)lists.freeswitch.org> Builiding freshly downloaded git version (git clone) on XP with VC2008 Express also generated lots of errors and mod_sophia can not be build. I just tried to build the solution directly without modify any setting or choose any project. On Mon, Jan 3, 2011 at 4:09 AM, Jeff Lenk <jeff(a)jefflenk.com<mailto:jeff@jefflenk.com>> wrote: What target are you trying to build? Post a log of the build or pastebin reference Sent from my Windows Phone ________________________________ From: Joao Leme Sent: Sunday, January 02, 2011 1:28 AM To: FreeSWITCH Users Help Subject: Re: [Freeswitch-users] Can't build on Windows 7 64bit C++ Express!? > Ok Thanks. Any idea why all the errors and why i can't build? I've built > before on Windows Vista 64bit and VS2008Pro with no problems but can't get > it to work on Express edition. > > On Sat, Jan 1, 2011 at 9:51 PM, babak yakhchali ><babak.freeswitch(a)gmail.com<mailto:babak.freeswitch@gmail.com>>wrote: > >> you just need to build the project in >> >> D:\gitRepos\2010exp-freeswitch\freeswitch\src\mod\languages\mod_managed\managed >> using vc# express, others should just work using vc++ >> >> _______________________________________________ >> FreeSWITCH-users mailing list >> FreeSWITCH-users(a)lists.freeswitch.org<mailto:FreeSWITCH-users@lists.freeswitch.org> >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >> http://www.freeswitch.org >> >> _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users(a)lists.freeswitch.org<mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org !DSPAM:4d21fef732761594845422!

2 1

Sangoma Cards or FXS gateway for high port density setup (~ 160 fxs)
by guru singh 03 Jan '11

03 Jan '11

Hi, Happy New Year! What would you recommend for a solution that requires ~160 fxs ports? Should I get a Sangoma A200, in fact 7 of them and put them on to my server or look for other products like Audiocodes/Patton fxs gateways etc? If I choose Sangoma cards, then I don't think I can set up a HA scenario since, all fxs ports will be on the FS box itself. But from what I've read people have horrible things to say about most gateway devices. They are prone to failure and the support is also very lax. So what good would be HA anyway, if one of these gateways fails and knocks 32 fxs ports off! Also I see that Sangoma is actively involved with the FreeSwitch project and digging through the mailing lists, I could see great support as well. Is it advisable to have 6-7 cards with 12 fxs modules each on my FS server? Any suggestions/pointers/heads-up would be really appreciated. Thanks guru

3 5

Re: [Freeswitch-users] tone_detect and dinging
by Anthony Minessale 03 Jan '11

03 Jan '11

It pre answers early media because it requires media to work. Activate it in execute_on_media instead On Dec 31, 2010 5:53 PM, "Madovsky" <infos(a)madovsky.org> wrote:

3 6

mode_nibblebill and mod_conference
by Madovsky 03 Jan '11

03 Jan '11

Is nibblebill works with conference ? I tried to set nibble_account and nibble_rate without success Thanks

1 0

voicmeail operator transfer
by Madovsky 03 Jan '11

03 Jan '11

in voicemail.conf.xml I have this <param name="operator-key" value="9"/> <param name="operator-extension" value="conference XML features"/> it works well but are all channel variables transferred also ? Thanks

2 4

ACL Problem
by Tim King 03 Jan '11

03 Jan '11

*I am getting this error sending calls from my Kamailio box on 192.168.0.250.* 2011-01-03 14:22:49.930896 [WARNING] sofia.c:6369 IP 192.168.0.250 Rejected by acl "domains" *Here is the contents of my ACL:* <configuration name="acl.conf" description="Network Lists"> <network-lists> <list name="lan" default="allow"> <node type="allow" cidr="192.168.0.250/32"/> </list> <list name="domains" default="deny"> <node type="allow" domain="$${domain}"/> <node type="allow" domain="192.168.0.250/32"/> </list> </network-lists> </configuration> *I do not understand why calls from this machine are being rejected. Kamailio and Freeswitch are on the same machine sharing the same IP. Any ideas what I am missing?*

3 2