just an off-topic question but it concenns mass provissioning ... does
anyone know if there is an open TR069 platform we can work on?
T.
On Wed, Nov 4, 2009 at 1:16 AM, Michael Collins wrote:
>
>
> On Tue, Nov 3, 2009 at 11:11 AM, Kristian Kielhofner <
> kristian.kielhof...@gmail.com> wrote:
>
nt:* Tue, November 3, 2009 10:27:39 PM
> *Subject:* Re: [Freeswitch-users] Sipura Codec Problem
>
> Sounds like bad planning. I would send out a memo to your users and
> have them fix it. I have raised a bug multiple times with Cisco g729a
> is NOT valid.
>
> /b
>
> On No
At some point the paint will be rubbed off the magic lamp.
/b
On Nov 3, 2009, at 1:11 PM, Kristian Kielhofner wrote:
> It appears that Tony has already added an option (amazing) BUT you
> should really be setup for central provisioning with an installed base
> that large... You'll eventually ha
THE BLOODY MADNESS!!! I can only stop if people start saying 'NO'. :)
/b
On Nov 3, 2009, at 1:21 PM, Anthony Minessale wrote:
> Don't forget the one where there was a typo in the one for G722 so
> now we are all required to emulate that typo by running a 16khz
> codec with 8khz timestamps a
Yah this one is LLLAME :P
We have some dyslexic engineers.
/b
On Nov 3, 2009, at 1:12 PM, Arsen Chaloyan wrote:
> Another issue is G726 bit packing. Again "some implementations" used
> wrong bit packing and RFC3551 tried to partially resolve this
> conflict introducing new payload forma
It appears that Tony has already added an option (amazing) BUT you
should really be setup for central provisioning with an installed base
that large... You'll eventually have issues that *NO* amount of
Tony/FreeSWITCH magic can fix.
On Tue, Nov 3, 2009 at 1:11 PM, Mariano de Llano
wrote:
> Yes,
On Tue, Nov 3, 2009 at 11:11 AM, Kristian Kielhofner <
kristian.kielhof...@gmail.com> wrote:
> It appears that Tony has already added an option (amazing) BUT you
> should really be setup for central provisioning with an installed base
> that large... You'll eventually have issues that *NO* amount
I am willing to support this with the note that its incorrect and will not
support it by default but update to trunk and try:
this should fix it for you, SIGH
On Tue, Nov 3, 2009 at 12:27 PM, Brian West wrote:
> Sounds like bad planning. I would send out a memo to your users and
> have them
so imagine how much money all those sipuras cost.
They get all the money *and* have a bug and we are free and are supposed to
break the rules for them.
On Tue, Nov 3, 2009 at 12:11 PM, Mariano de Llano wrote:
> Yes, that was my first option, but there many endpoints that I'm not
> able to confi
Sounds like bad planning. I would send out a memo to your users and
have them fix it. I have raised a bug multiple times with Cisco g729a
is NOT valid.
/b
On Nov 3, 2009, at 12:11 PM, Mariano de Llano wrote:
> Yes, that was my first option, but there many endpoints that I'm not
> able to c
Hi,
I'm having a problem with a Sipura, it is sending for the G729 the
tag "G729a" witch is not correct due the RFC.
Media Attribute (a): rtpmap:18 G729a/8000
FS is returning (200OK)
Media Attribute (a): rtpmap:96 G729/8000
I think that the problem is that FS is not matching the codec, so i
ue, November 3, 2009 10:27:39 PM
Subject: Re: [Freeswitch-users] Sipura Codec Problem
Sounds like bad planning. I would send out a memo to your users and
have them fix it. I have raised a bug multiple times with Cisco g729a
is NOT valid.
/b
On Nov 3, 2009, at 12:11 PM, Mariano de Llano wrote:
Yes, that was my first option, but there many endpoints that I'm not
able to configure. Basically it's a broadband solution where I have
like 1000 endpoints that are out of my provisioning.
Thanks,
M
On 03/11/2009, at 14:58, Brian West wrote:
> FIx your sipura to NOT include the a in the cod
FIx your sipura to NOT include the a in the codec its in the admin
section of the UI on the ATA.
/b
On Nov 3, 2009, at 11:47 AM, Mariano de Llano wrote:
> Hi,
>
> I'm having a problem with a Sipura, it is sending for the G729 the
> tag "G729a" witch is not correct due the RFC.
>
> Media Attri
I think you can edit the prefs in your sipura and change it to the correct
string.
On Tue, Nov 3, 2009 at 11:47 AM, Mariano de Llano wrote:
> Hi,
>
> I'm having a problem with a Sipura, it is sending for the G729 the
> tag "G729a" witch is not correct due the RFC.
>
> Media Attribute (a): rtpm
15 matches
Mail list logo
