Yes, we are probably going to use a separate FS box as a SBC / B2BUA.
-----Original Message----- From: Tony Graziano [mailto:tgrazi...@myitdepartment.net] Sent: Tuesday, April 20, 2010 6:07 PM To: mra...@gmail.com; kenful...@icstechnologysolutions.com Cc: sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] g.729 If you are really serious about using it you should invest in a device for trunking and remote users that performs transcoding. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: sipx-users-boun...@list.sipfoundry.org <sipx-users-boun...@list.sipfoundry.org> To: Ken Fulmer <kenful...@icstechnologysolutions.com> Cc: sipx-users@list.sipfoundry.org <sipx-users@list.sipfoundry.org> Sent: Tue Apr 20 18:56:36 2010 Subject: Re: [sipx-users] g.729 If you add G729 to the codec list for FreeSWITCH (assuming you care about G729 support for bridged calls and you do not want to hear silence for MOH and assuming that G729 support implies FreeSWITCH will stream MOH using G729), you may want to make sure it is also added to the allowable codec set for sipxbridge. See the advanced screen of sipxbridge configuration. On Tue, Apr 20, 2010 at 5:13 PM, Ken Fulmer <kenful...@icstechnologysolutions.com> wrote: > Yeah, the codec appeared in the web browser menu, but I couldn't get it to > work either. > > > > > > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Josh Patten > Sent: Tuesday, April 20, 2010 4:09 PM > Cc: sipx-users@list.sipfoundry.org > Subject: Re: [sipx-users] g.729 > > > > I believe the newer models support iLBC, but I couldn't get it working. > > > Josh Patten > > Assistant Network Administrator > > Brazos County IT Dept. > > (979) 361-4676 > > On 4/20/2010 4:08 PM, Ken Fulmer wrote: > > We are using Polycom phones and I don't think they support speex or ILBC > (at > least not all the models). > > > ; > > > > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Josh Patten > Sent: Tuesday, April 20, 2010 3:57 PM > To: sipx-users@list.sipfoundry.org > Subject: Re: [sipx-users] g.729 > > > > FYI I just confirmed using the X-Lite Client that FreeSWITCH supports both > the narrowband and wideband speex codecs. From what I understand it's > lower > bandwidth than G.729: > http://lists.xiph.org/pipermail/speex-dev/2006-May/004453.html > > I couldn't get iLBC to work with FreeSWITCH/Polycom/xLite so I gave up on > it. > > Josh Patten > > Assistant Network Administrator > > Brazos County IT Dept. > > (979) 361-4676 > > On 4/20/2010 1:29 PM, Josh Patten wrote: > > Does your ITSP support speex or iLBC? If so, consider the following: > > in /etc/sipxpbx/freeswitch/conf/sip_profiles/sipX_profile.xml: > > <param name="codec-prefs" value="G722,p...@20i,p...@20i,speex,L16"/> > > speex is supported by FreeSWITCH and it's a very robust low bandwidth > codec > albeit at some CPU cost. It's also already preconfigured in sipX's > implementation on FreeSWITCH. Adding iLBC should be as simple as changing > that line and possibly a few others in other FreeSWITCH config files by > adding i...@30i to that list. > > Perhaps you could do G.729 for phone-to-phone calls and then let > FreeSWITCH > do speex? Am I missing a reason why this would not be possible? > > > Josh Patten > > Assistant Network Administrator > > Brazos County IT Dept. > > (979) 361-4676 > > On 4/20/2010 1:13 PM, Michael Scheidell wrote: > > I really ONLY care about AA/Voicemail/Conferencing (since everything else > seems to work). > I am assuming the only time I will need it is in freeswitch, caller using > G.729, hits AA/vmail or conference. I get 4 licenses, I am assuming 5th > concurrent caller (using G.729) will probably not hear anything. in the > case of conferencing, oh well. in the case of AA or vmail, maybe he will > call back. > maybe 10 licenses ($100) isn't all that much to spend if it works. > > I thought I did turn off everything in voip.ms except G729 and the caller > can't reach AA or Vmail if the user doesn't answer. > (you on 4.2.0 yet?) > > On 4/20/10 2:08 PM, Eric Varsanyi wrote: > > I may be misunderstanding your configuration, but it seems like if you > don't > care about AA/Voicemail/Conferencing then the freeswitch license isn't > going > to help (or hurt) you at all. > > > > If your remote callers would be better off with a different codec you > could > try to limit the codecs their endpoint s/w or h/w will allow (ie: don't > advertise g711 at all, just uLaw and g729). If your remote users are on > POTS > then your issue is between you and your ITSP and you could limit your ITSP > configuration to the codecs you like (for instance with voip.ms I can pick > which codecs it will accept, I turned off g711 and gsm so now it always > negotiates uLaw which is pretty good; I wish they had g722 as an option > too > though). > > > > > > -- > Michael Scheidell, CTO > Phone: 561-999-5000, x 1259 >> | SECNAP Network Security Corporation > > Certified SNORT Integrator > > 2008-9 Hot Company Award Winner, World Executive Alliance > > Five-Star Partner Program 2009, VARBusiness > > Best Anti-Spam Product 2008, Network Products Guide > > King of Spam Filters, SC Magazine 2008 > > > > ________________________________ > > This email has been scanned and certified safe by SpammerTrapR. > For Information please see http://www.secnap.com/products/spammertrap/ > > ________________________________ > > > > > _______________________________________________ > > sipx-users mailing list sipx-users@list.sipfoundry.org > > List Archive: http://list.sipfoundry.org/archive/sipx-users > > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > > sipXecs IP PBX -- http://www.sipfoundry.org/ > > > > > > _______________________________________________ > > sipx-users mailing list sipx-users@list.sipfoundry.org > > List Archive: http://list.sipfoundry.org/archive/sipx-users > > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > > sipXecs IP PBX -- http://www.sipfoundry.org/ > > _______________________________________________ > sipx-users mailing list sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- M. Ranganathan _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
