Has any one tried this codec on MNF using a Grandstream ATA?

phred01 writes...

Has any one tried this codec on MNF using a Grandstream ATA?

Why, what's the problem? Is your call going to voicemail?

/index.cfm?a=wiki&tag=Update_Pro

phred01 writes...

Has any one tried this codec on MNF using a Grandstream ATA

I would also like to hear everyone's thoughts on the Quality of Service using this codec?

Any problems.

It is a newer codec, with little to none Hardware support, so good to see devices appearing that support it.

Can everyone give it a shot, and let me know?

I have used it with the latest SJphone softphone when my ADSL service was shaped to 64k and found it to be excellent.

In fact I could not tell the difference with when my service was unshaped so it is a pretty good low bandwidth codec.

Hi,
I'm not using it with an ATA, but am now using it will all my trixbox boxes, with very good results.

The only problem I'm having with it is DTMF tones don't seen to work, even when set to RFC2833.

Apart from that, the calls are clear & my clients are happy because they can cram more calls down their internet connections.

Regards,
Josh

Just got a Ht-496 connected via sat and using MNF (iLBC codec) impressed with voice quality. The only downside bit like 2 way radio; one needs to refrain from talking over one another.

phred01 writes...

Has any one tried this codec on MNF?

Hi phred01

iLBC is also supported with the Minitar MVA11A ATA.

http://www.minitar.com/index.php?maincat=product&cat=networking&prod=n_mva11a&page=1

Cheers

Brent Spargo writes...

I would also like to hear everyone's thoughts on the Quality of Service using this codec?

I have been with MNF for several years now and on VSat.

I run, Grandstream BT100 series phones, Linksys PAP2 Ata's and Minitar units..

I tried the iLBC codec on all of the units here with varying results..
The Grandstream units didn’t work for incoming from landline..
The PAP2 were a similar result with a lower voice quality.
The Minitar with the iLBC codec and ver8 firmware didn’t work well for incoming from landline

All calls out on the VSat over Ipstar 512 plan were perfect..Incoming is where the problem is..

I use G711a for VoIP and G711u for FoIP (Fax) on VSat using Ipstar

Phred01 contacted me re the iLBC and I have had different results to him,
Different hardware gives different results.
When doing test calls to people that contact me I give them the details of the equipment that is in use and the configuration details of same.. I have 3 different units connected to the system and can change the configuration to demonstrate the different arrangements

All tests are done using the Ipstar 512 plan as this is the predominant choice of many in the bush.. I recommend that they go to the 1 meg plan if finances allow it

Paul

Ukurrie writes...

Incoming is where the problem is

Is it possible there is an incompatability here between the prefered codec and Supported codecs?

Brent Spargo writes...

Is it possible there is an incompatability here between the prefered codec and Supported codecs?

As mobile phones use iLBC codec why isn't the incompatibility experienced over the whole telephone network?

phred01 writes...

As mobile phones use iLBC codec

Two things:

1. Do they? – I thought they used some type of GSM Codec?

2. I wanted to empasise that the user can, at their descretion (and how a device is configured) to set a prefered codec, and the list of supported codecs.

Calls may very well fail if a common codec cannot be negotiated.

Brent Spargo writes...

1. Do they? – I thought they used some type of GSM Codec?
Ok 2 codecs but not g711 g729 g726 or g723
correct me if wrong
2. I wanted to empasise that the user can, at their descretion (and how a device is configured) to set a prefered codec, and the list of supported codecs.
Very good reason why we wish to limit to a specific codec sat BB is limited in BW and can have hi contention issues.

Calls may very well fail if a common codec cannot be negotiated.
So what u are saying if a mobile phone running gsm or iLBC cannot connect to a service running g711 g729 g726 or g723.
Haven't experience a problem in this area.
As my latest test revealed iLBC (fixed) to g711 doesn't connect. Yet same equipment g711 to iLBC does. Why?

phred01 writes...

As my latest test revealed iLBC (fixed) to g711 doesn't connect. Yet same equipment g711 to iLBC does. Why?

Maybe you aren't understanding the difference between a Prefered Codec (the codec the user has set to be used for outgoing calls specifically) and supported codecs (the list of codecs that the service can support)

So in this instance:

1. Ensure both parties support the full plethora of Voip codecs and calls should not fail.

@#127820 Brent Spargowrites...
Maybe you aren't understanding the difference between a Prefered Codec (the codec the user has set to be used for outgoing calls specifically) and supported codecs (the list of codecs that the service can support)?

Ok this your explanation for voip to voip connections. But still u haven explained mobile phone connections to the rest of the phone network. Is there a special treatment how the connections are made? If so, why can't iLBC be handle the same way?

phred01 writes...

If so, why can't iLBC be handle the same way?

Yea, but all calls to the PSTN (landline or mobile) for via the TDM network, with is G711a... the GSM codec is only implemented over the GSM radio network from the mobile operator to the handset.

iLBC is not used on the GSM network, it's specifically a GSM 9.6kbps or 19.2kbps codec variant...

Either way, MNF should support a call with starts as iLBC at the VoIP CPE, then MNF will convert it to G711a to put on the PSTN, then the mobile operator will convert it to the GSM codec for the last hop to the handset.

It looks like MNF are only doing the connection bit. Not a real support of all the different codecs. If MNF wanted to stitch up the market, they should do the conversion to G711 for iLBC users and vicky versa. So far the connections that support iLBC are very good much better than the landline. Strange Freshtel claim they don't support iLBC yet folk in Norfolk Is have been using iLBC for sometime. Maybe everyone has a different definition of support!

Brent Spargo writes...

Is it possible there is an incompatability here between the prefered codec and Supported codecs?

I use Ipstar 2way satellite (4yrs) and MyNetFone VoIP service (5yrs)

It would seem that the original iLBC codec that I tried wasn’t totally compatible for use on 2 way satellite..Since the upgrade of firmware and iLBC codec from Quentin/Billion, all has run smoothly and the quality is the same as using the G711a codec, with the major difference being it consumes around 1/3rd bandwidth as per the G711 codec..

At this time, the only ATA or SIP phone with iLBC codec that performs properly on Ipstar 2 way satellite is the Minitar ATA, all the other devices that are used for testing need to run G711 codec to work clearly on VSat without using the ISP’s CBR IP Address which is for their respective in-house VoIP service.
Some minor improvements are gained by having the CBR and address enabled in the Modem

Firmware used is Ver.13 and iLBC 2 from Quentin.
The former Firmware 8 and iLBC 1 doesn’t work for incoming calls

Paul

Does this mean that with iLBC2 incoming calls are working. What about a MNF 2 MNF connection iLBC --> g711?

lemming86_au writes...

The only problem I'm having with it is DTMF tones don't seen to work, even when set to RFC2833.

INFO seems to working for me with iLBC (but I'm with GoTalk) just thought it might help and you could give it a try with MNF.

phred01 writes...

Does this mean that with iLBC2 incoming calls are working. What about a MNF 2 MNF connection iLBC --> g711?

Everything at my end is working extremely well, no matter to where the call is place to or where it comes from.. MNF to MNF AU to UK and USA unit’s are very good..