2011/6/14 George Niculae :
> 2011/6/8 Irena Dolovčak :
>> here is the log..
>>
>
> sipXbridge responds with 488 since it cannot find audio media type in
> INVITE, can you take a pcap to see exactly the SIP message that hits
> sipXbridge?
>
Or it is rejected because there are no media formats that
2011/6/8 Irena Dolovčak :
> here is the log..
>
sipXbridge responds with 488 since it cannot find audio media type in
INVITE, can you take a pcap to see exactly the SIP message that hits
sipXbridge?
George
___
sipx-users mailing list
sipx-users@list.sip
2011/6/8 Irena Dolovčak :
> 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
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 P
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,
On Wed, Jun 1, 2011 at 12:33 PM, Irena Dolovčak
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 ab
Thanks George,
That would be great. Yes, i think that it would solve our problem.
Thanks.
Regards,
Irena
On Wed, Jun 1, 2011 at 11:13 AM, George Niculae wrote:
> On Wed, Jun 1, 2011 at 10:48 AM, Irena Dolovčak
> wrote:
> >
> > this mybuddy limitation/bug is a real problem for us. i know th
On Wed, Jun 1, 2011 at 10:48 AM, Irena Dolovčak
wrote:
>
> this mybuddy limitation/bug is a real problem for us. i know that in the
> states this isn'a a real problem, but here in europe things are much
> different. we have a lot of small international ITSPs that support PCMU, but
> all the big an
this mybuddy limitation/bug is a real problem for us. i know that in the
states this isn'a a real problem, but here in europe things are much
different. we have a lot of small international ITSPs that support PCMU, but
all the big and serious ITSPs support only PCMA.
this suggestion that includes
On Tue, May 31, 2011 at 10:53 AM, Irena Dolovčak
wrote:
> Thanks Tony,
> you were right, myBuddy offeres only PCMU.
> we opened a jira..
> Is there perhaps a way to "hack" the codec and force myBuddy to use the PCMA
> codec?
>
> did anybody tried something like this?
grep/modify the source and bu
Thanks Tony,
you were right, myBuddy offeres only PCMU.
we opened a jira..
Is there perhaps a way to "hack" the codec and force myBuddy to use the PCMA
codec?
did anybody tried something like this?
On Tue, May 31, 2011 at 1:47 PM, Tony Graziano wrote:
> I thought I h dseen on here that mybud
I thought I h dseen on here that mybuddy was only offering uLaw. If
you have a call trace from sipx, you could verify exactly what mybuddy
was offering.If it is not offering aLaw as a codec choice, that would
explain a lot. I don't however know if mybuddy is the problem. I would
imagine that would
Hi,
we have a problem when it comes to making a call via mybuddy. what we are
trying to do is to establish a call between two cell phones through sipxecs.
this should be accomplished through this command in mybuddy:
'call (cell-number-1) (cell-number-2)', where the first number is the phone
that w
13 matches
Mail list logo
