Hi George, It seems that the patch that you provided us wasn't successful after all. With this patch it seems that the INVITe has PCMA and PCMU offered to the ITSP server. Logs clearly show that SDP contains both of the mentioned codecs, but people from the ITSP say that we are still sending only PCMU. This was very puzzling for us, so we removed PCMU from the SIP trunk service. Unfortunately, the same problem repeats itself as before: when we remove PCMU from the SIP trunking service, sipxecs won't send the INVITE through the trunk.
>From the logs, we can see that the initial INIVTE that MyBuddy made has both PCMA and PCMU, and that INVITE retains both codecs while it goes from one service to another. Until it comes to the SIP trunking (port 5090). SIP trunking service returns '488 Not Acceptable' message. This is very weird because all the INVITE's show that both codecs are present, but for some reason trunking service doesn't accept it. Regards, Irena 2011/6/1 Irena Dolovčak <[email protected]> > Hi George, > > We have replaced the file, now MyBuddy is using PCMA, but something is > still wrong. We have contacted the ITSP provider. We'll let you know what > was wrong. > > I attached the new log. > > Regards, > Irena > > > On Wed, Jun 1, 2011 at 3:29 PM, George Niculae <[email protected]> wrote: > >> Try this one please, I think I messed up the files >> >> George >> >> On Wed, Jun 1, 2011 at 4:17 PM, George Niculae <[email protected]> wrote: >> > Hi Irena, >> > >> > have you removed the old jar entirely and put this one? Can you >> > restart the whole sipxecs just to be sure? >> > I modified the INVITE to include PCMA but don;t see it in the pcap you >> > sent, it looks exactly like the old one so the change could not have >> > been accounted. >> > >> > Regards >> > George >> > >> > On Wed, Jun 1, 2011 at 3:44 PM, Irena Dolovčak < >> [email protected]> wrote: >> >> Hey George, >> >> >> >> Unfortunately it didn't work.. MyBuddy is still using PCMU.. >> >> I attached a wireshark log. >> >> Regards, >> >> Irena >> >> >> >> On Wed, Jun 1, 2011 at 11:41 AM, George Niculae <[email protected]> >> wrote: >> >>> >> >>> On Wed, Jun 1, 2011 at 12:33 PM, Irena Dolovčak >> >>> <[email protected]> wrote: >> >>> > Thanks George, >> >>> > >> >>> > That would be great. Yes, i think that it would solve our problem. >> >>> >> >>> Please find attached, just replace the old sipXcallController.jar >> >>> within usr/share/java/sipXecs/sipXrest/plugins/ and restart call >> >>> controller. >> >>> Not sure about other side effects though, but let me know if this >> >>> solves your issue >> >>> >> >>> George >> >>> >> >>> _______________________________________________ >> >>> sipx-users mailing list >> >>> [email protected] >> >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> >> >> >> >> >> >> -- >> >> Irena Dolovčak >> >> >> >> _______________________________________________ >> >> sipx-users mailing list >> >> [email protected] >> >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> >> > >> > > > > -- > Irena Dolovčak > -- Irena Dolovčak
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
