I'd like to hear his approach.

In 4.4 freeswitch is not exactly sipx dependent and can be
upgraded/maintained separately from sipx if desired.

On 4.2.1 its a different story.
============================
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431

Email: [email protected]

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: [email protected]
<[email protected]>
To: Michal Bielicki <[email protected]>; Discussion list for
users of sipXecs software <[email protected]>
Sent: Wed Jan 26 10:40:54 2011
Subject: Re: [sipx-users] Codec/freeswitch problems

On 1/26/2011 8:29 AM, Michal Bielicki wrote:
> Am 26.01.2011 um 04:09 schrieb Matthew Kitchin (usenet/public):
>
>> After talking with Tony, I unfortunately know I can't put a G729
>> freeswitch license in the version of freeswitch that runs in sipx 4.2.1.
>> I got Verizon to up my bandwidth, so I can switch sipxbridge back to
>> blocking G729. I can't really do this at my low bandwidth sites though.
> You can easily use a newer freeswitch version and get g729 licenses for
> it. If you do not expect help at midnight CET I can easily help you set
> that up, its pretty simple.
>
> cheers
> Michal
>
I have a test system where I can try this, so I would love some
instructions on how to upgrade freeswitch and set this up.
I am up and running on G711 at my main site today, so my major crisis is
resolved.
I sincerely appreciate your offer to help. If I can get some good
experience with this, I will be more than happy to be a source of
information for others that have the same issue.
>> Does anyone have any interest in investigating why the calls die during
>> transfer, hold, etc. and why they behave differently with the different
>> polycom firmwares? I will be glad to provide the data, logs, testing, and
>> such. I'm just not too good at troubleshooting sip. If it doesn't
>> interest anyone, I guess I'm stuck running G711 until the version that
>> supports G729 freeswitch licensing comes out. Thanks all.
>> ------Original Message------
>> From: Matthew Kitchin (public/usenet)
>> To: Discussion list for users of sipXecs software
>> Subject: Codec/freeswitch problems
>> Sent: Jan 25, 2011 4:00 PM
>>
>> I'm running sipXconfig (4.2.1-018971 2010-08-17T02:20:18 build20),
>> sipxbridge, Verixon VOIP, Polycom 450s, 550s, and 1 650.
>>
>> It has been a rough week. I'll leave out some of the details as to how I
>> got where I am, and just describe the problem.
>> I have sipxbridge set to allow all codecs.
>> Phones are set to use G722, G729, and G711 in that order.
>> The goal is to have G722 for internal communication and G729 for calls
>> to the PSTN.
>> Verizon does not allow G722. They do support codec renegotiation during
>> a call.
>> I'm having a variety of problems that I believe may have something to do
>> with freeswitch (within sipx) not supporting G729.
>> I have different symptoms with different firmware.
>> 3.1.3c - Call drops when performing a blind transfer - destination phone
>> rings one time. Hold works fine.
>> 3.2.1b - Call cannot be retrieved from hold. Transfers do work.
>> 3.2.4 - Call drops when performing a blind transfer - destination phone
>> rings one time. Hold works fine.
>>
>> If I put the defaults back in sipxbridge to block G729, everything seems
>> fine.
>>
>> I upgraded to 4.2.1 from 4.0.4 a few months ago. We were going over our
>> allotted bandwidth and dropping calls. That was when I realized the new
>> default setting in sipxbridge blocked G729. We need to use G729, so I
>> blanked out that field. I'm guessing that is when the things above
>> started going wrong. I have no idea why the different firmwares behave
>> differently. I'm running 3.2.1b right now with unhappy users. I've got
>> an urgent request in to Verizon to up our bandwidth on this circuit, but
>> that can't be my long term solution.
>> I will be glad to provide wireshark or merged logs for any of these
>> scenarios. I tried sipx-trace, but I wasn't able to get a lot of info. I
>> have it on an isolated system, so the logs aren't full of unrelated
>> stuff.
>> I've read through this:
>> http://wiki.sipfoundry.org/display/sipXecs/G729
>> and I have looked at some of the posts in the past few months about
>> G729. Would you assume this is a G729 issue? From what I've read, it
>> doesn't look like I have any options for licensing G729 for freeswitch
>> on sipx 4.2.1.
>> My brain is just about scrambled eggs right now.
>> I'm really looking for:
>> 1) basic thoughts on my issue if anyone can enlighten me
>> 2) a possible fix related to firmwares, in case there is something along
>> those lines that would help me
>> 3) long term solution for licensing g729 in freeswitch (assuming I am
>> correct in what the issue is)
>>
>> Thanks as always,
>> Matthew
>>
>>
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
> Michal Bielicki
> Geschäftsführer / CEO
>
> Seventh Signal Ltd.&  Co. KG
> Weigandufer 45, Büro 115, D-12059 Berlin
> Voice: +49 30 60988730
>
> Amtsgericht Charlottenburg HRA 44413 B
> Ust.-ID: DE266981999
> Geschäftsführer: Michal Bielicki
> Persönlich Haftende Gesellschafterin:
> Seventh Signal Ltd, 69 Great Hampton St. Birmingham,
> B18 6EW, GB, Company Nr.: 06889439
> WWW.: http://www.seventhsignal.de
>

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to