(On Bberry, excuse top post) I had to go ahead and make the change at lunch time and only kill about 10 calls. It seems to be working as it should. MOH is working. Verizon will definitely renegotiate to any of their supported codecs on the fly. Is that what your statement below means? -----Original Message----- From: "M. Ranganathan" <[email protected]> Sender: [email protected] Date: Wed, 19 Jan 2011 18:23:04 To: Discussion list for users of sipXecs software<[email protected]> Reply-To: Discussion list for users of sipXecs software <[email protected]> Subject: Re: [sipx-users] upgrade 4.0.4 -> 4.2.1 and G729 no longer passes through sipXbridge
On Wed, Jan 19, 2011 at 11:32 AM, Matthew Kitchin (public/usenet) <[email protected]> wrote: > Maybe this has been discussed, or I'm missing something obvious. > I built my corporate system on 4.0.4. I wanted to use G722 internally, > G729 for external, and the ability to renegotiate to G711 if ITSP > (Verizon requested it). > Verizon doesn't do G722, so simply putting the codecs at the phone group > to 722, 729, then 711 worked perfectly. > We upgraded to 4.2.1 a month or so ago. We started going over our > allotted bandwidth on our VOIP circuit and dropping calls. After looking > at a wireshark, I saw that all calls were using G711. > I poked around and found this new (I think it is new) feature: > Devices, SBC Routes, sipXbridge-1, SIP, Show Advanced Settings > ,Permitted Codecs > The default setting was "PCMU,PCMA,G722,L16" Those are free-switch supported default codecs. If you pick G729, MOH may not work for certain ITSPs that return only the negotiated codec for In-dialog INVITE(no SDP). This is actually an error but some ITSPs do it. > On a test machine, I blanked this field, and now calls are using G729 as > expected. > If I understand it correctly, the upgrade puts in a default setting that > will not allow sipXbridge to use G729. If that is the case, wouldn't the > safer thing been to leave that field blank and maybe advise the user of > the new feature? Am I correct that blanking out that field should make > sipXbridge behave more like 4.0.4 with respect to codec negotiation? > > Thanks as always, > Matthew > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- M. Ranganathan _______________________________________________ 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/
