IMG 1010 - Vocoder Information

Owned by Kelli Higdon
Last updated: Mar 28, 2024
5 min read

 

 

The IMG 1010 has two DSP chips which provide enough capability to handle all announcements, all call progress tones, and all call setup tones needed to perform our call load performance tests. Each codec uses a different amount of resources from the resource pool in the IMG 1010. Below are a few tables displaying the codecs supported, the profiles supported for each codec, and the amount of resources available for each profile.

The IMG 1004 has a single DSP chip which provides enough capability to handle all announcements, all call progress tones, and all call setup tones needed to perform our call load performance tests. Each codec uses a different amount of resources from the resource pool in the IMG 1004. Below are a tables displaying the codecs supported, the profiles that are supported for each codec, and the amount of resources available for each profile.

VoIP Resource Profiles:

Codecs supported by Profile number

Codec

Licensing Required

Profile 5

Profile 6

Profile 7

Profile 8

Codec

Licensing Required

Profile 5

Profile 6

Profile 7

Profile 8

G.711 alaw

No

Yes

Yes

Yes

Yes

G.711 ulaw

No

Yes

Yes

Yes

Yes

G.723 5.3 kbps

No

Yes

Yes

Yes

Yes

G.723 6.3 kbps

No

Yes

Yes

Yes

Yes

G.729

No

Yes

Yes

Yes

Yes

G.729E

No

Not Supported

Yes

Yes

Not Supported

iLBC 20 ms

No

Not Supported

Yes

Yes

Not Supported

iLBC 30 ms

No

Not Supported

Yes

Yes

Not Supported

AMR

Yes

Not Supported

Not Supported

Yes

Yes

EVRC

Yes

Not Supported

Not Supported

Yes

Not Supported

GSM - FR Static

No

Not Supported

Yes

Yes

Yes

GSM - FR Dynamic

No

Not Supported

Yes

Yes

Yes

G.726-32/G.721 Static

No

Yes

Yes

Yes

Yes

G.726-32/G.721 Dynamic

No

Yes

Yes

Yes

Yes

Clear Channel Codec

No

Yes

Yes

Yes

Yes

Codecs supported by protocol:

The IP Bearer Profile object is used to define a set of VoIP Parameters to be used in each individual SIP or H.323 Channel Group configured. When configuring the IP Bearer Profile object, ClientView allows the user to configure a list of vocoders/codecs that this channel group will support. These are termed vocoder entries. Attributes such as payload type and size (preferred, minimum, and maximum) are configured in the vocoder entry. When there are multiple vocoder entries configured under the IP Bearer Profile object the IMG will start with the topmost entry and work its way down the list until codec negotiation with the far end gateway is satisfied. The user can set the priority of each vocoder entry by moving the entry up in the list. See IMG 1010 - Changing Vocoder Order in an IP Profile for information on setting the priority. The table below displays on a very high level which codec is supported in either the SIP or H.323 protocol. For more in depth tables that display the codec supported by individual profile, see tables in next section below.

 

CODEC

SIP

H.323

CODEC

SIP

H.323

G.711 alaw/ulaw

Yes

Yes

G.723 5.3Kbps

Yes

Yes

G.723 6.3Kbps

Yes

Yes

G.729A, G.729A/B

Yes

Yes

G.729E, G.729E/G

Yes

Not Supported

T.38

Yes

Yes

iLBC 20 ms

Yes

Not Supported

iLBC 30 ms

Yes

Not Supported

AMR

Yes

Not Supported

EVRC

Yes

Not Supported

G.726-32/G.721 Static Payload

Yes

Not Supported

G.726-32/G.721 Dynamic Payload

Yes

Not Supported

GSM-FR Static Payload

Yes

Not Supported

GSM-FR Dynamic Payload

Yes

Not Supported

Clear Channel Codec

Yes

Not Supported

Using the AMR-NB resource in connection with one or more Sangoma products mentioned herein does not grant the right to practice the AMR-NB standard. To seek a patent license agreement to practice the standard, contact the VoiceAge Corporation at http://www.voiceage.com/licensing.php

 IP Port Density supported by combination of Codec and Profile Number

The next two tables display the number of IP ports or port density per profile for each codec supported on the IMG 1010 and/or IMG 1004. Note that each port can be used to connect with a subsequent port on the TDM leg. For a breakdown of IP to IP Transcoding sessions supported please see the information in the IMG 1010 - Transcoding topic.

Note: The individual profiles (Profile 5, Profile 6, etc) are configured on the IMG by setting either the parameter Host_1010_Flag on the IMG 1010 or the Host_1004_Flag on the IMG 1004. These parameters are located in the dhcpd.conf file in /etc. See IMG 1010 - Setting Host Flags link for more information on configuring IMG for a specific profile.

IMG 1004:

Supported Codecs

Profile 5

SRTP Off

Profile 5

SRTP On

Profile 6

SRTP Off

Profile 6

SRTP On

Profile 7

SRTP Off

Profile 7

SRTP On

Profile 8

SRTP Off

Profile 8

SRTP On

Supported Codecs

Profile 5

SRTP Off

Profile 5

SRTP On

Profile 6

SRTP Off

Profile 6

SRTP On

Profile 7

SRTP Off

Profile 7

SRTP On

Profile 8

SRTP Off

Profile 8

SRTP On

G.711 a-law

128

84

84

72

84

72

120

84

G.711 u-law

128

84

84

72

84

72

120

84

G.723.1 5.3kbps

128

84

84

72

84

72

120

84

G.723.1 6.3kbps

128

84

84

72

84

72

120

84

G.726-32/G.721

128

84

84

72

84

72

120

84

G.729 a/b/e

128(G.729e=*N/S)

84(G.729e=*N/S)

84

72

84

72

120(G.729e=*N/S)

84(G.729e=*N/S)

iLBC

*N/S

*N/S

84

72

84

72

*N/S

*N/S

GSM-AMR

*N/S

*N/S

*N/S

*N/S

84

72

120

84

GSM-FR

*N/S

*N/S

84

72

84

72

120

84

EVRC

*N/S

*N/S

*N/S

*N/S

84

72

*N/S

*N/S

Clear Channel

128

84

84

72

84

72

120

84

*N/S = Not Supported

 IMG 1010:

The numbers displayed in the table below is for an IMG 1010 with one VoIP module installed. If the IMG 1010 has only two VoIP Modules installed then the numbers displayed below will be doubled.

 

Supported Codecs

Profile 5

SRTP Off

Profile 5

SRTP On

Profile 6

SRTP Off

Profile 6

SRTP On

Profile 7

SRTP Off

Profile 7

SRTP On

Profile 8

SRTP Off

Profile 8

SRTP On

Supported Codecs

Profile 5

SRTP Off

Profile 5

SRTP On

Profile 6

SRTP Off

Profile 6

SRTP On

Profile 7

SRTP Off

Profile 7

SRTP On

Profile 8

SRTP Off

Profile 8

SRTP On

G.711 a-law

512

336

336

288

336

288

480

336

G.711 u-law

512

336

336

288

336

288

480

336

G.723.1 5.3kbps

512

336

336

288

336

288

480

336

G.723.1 6.3kbps

512

336

336

288

336

288

480

336

G.726-32/G.721

512

336

336

288

336

288

480

336

G.729 a/b/e

512(G.729e=*N/S)

336(G.729e=*N/S)

336

288

336

288

480(G.729e=*N/S)

336(G.729e=*N/S)

iLBC

*N/S

*N/S

336

288

336

288

*N/S

*N/S

GSM-AMR

*N/S

*N/S

*N/S

*N/S

336

288

480

336

GSM-FR

*N/S

*N/S

336

288

336

288

480

336

EVRC

N/S

*N/S

*N/S

*N/S

336

288

*N/S

*N/S

Clear Channel

512

336

336

288

336

288

480

336

*N/S = Not Supported

Example 1:

The IMG 1004 is configured to use Profile 5, SRTP is disabled, and the codec being used is G.711 u-law. The maximum number of IP channels available 128.

Example 2:

The IMG 1010 is configured to use Profile 5, SRTP is disabled, and the codec being used is G.726-32. The maximum number of IP ports available is 1024.

Breakdown of Resources Supported by DSP Chip.

IMG 1010 Resources Supported by Profile Number (4 Chip Module Installed)

Profile Number

Resources Supported

Channels per DSP

Channels per Module

Profile Number

Resources Supported

Channels per DSP

Channels per Module

PROFILE 5

512 Resources

128

512

PROFILE 6

336 Resources

84

336

PROFILE 7

336 Resources

84

336

PROFILE 8

480 Resources

120

480

IMG 1010 Resources supported by Profile Number (2 Chip VoIP Module Installed)

Profile Number

Resources Supported

Channels per DSP

Channels per Module

Profile Number

Resources Supported

Channels per DSP

Channels per Module

PROFILE 5

256 Resources

128

256

PROFILE 6

168 Resources

84

168

PROFILE 7

168 Resources

84

168

PROFILE 8

240 Resources

42

84

 IMG 1004 Resources Supported by Profile Number

IMG 1004 supports only 1 DSP chip which is embedded on the IMG 1004 Motherboard. See table below.

Profile Number

Resources Supported

Channels per DSP

Profile Number

Resources Supported

Channels per DSP

PROFILE 5

128 Resources

128

PROFILE 6

84 Resources

84

PROFILE 7

84 Resources

84

PROFILE 8

120 Resources

120

IMG 1010 Resources Supported by Profile Number with SRTP Enabled

Profile #

VoIP Module Resources (SRTP Enabled)

VoIP Module Resources (SRTP Disabled)

Profile #

VoIP Module Resources (SRTP Enabled)

VoIP Module Resources (SRTP Disabled)

Profile 5

336 Resources

512 Resources

Profile 6

288 Resources

336 Resources

Profile 7

288 Resources

336 Resources

Profile 8

336 Resources

480 Resources

 

Codec Payload Size:

The table below includes information on the payload sizes in milliseconds of the codecs supported by the IMG. The payload size can be changed in ClientView in increments of 10 ms.

 

For example:

G.723 5.3 kbps codec can have the payload size of 10,20,30,40,50, or 60

 

Table 3: Codecs supported and Min/Max/Preferred payload sizes

Payload Type/Codec

Preferred Payload Size

Minimum Payload Size

Maximum Payload Size

Payload Type/Codec

Preferred Payload Size

Minimum Payload Size

Maximum Payload Size

AMR (SIP ONLY)

20 ms

20 ms

20 ms

EVRC (SIP ONLY)

20 ms

20 ms

20 ms

G.711 alaw

20 ms

10 ms

30 ms

G.711 ulaw

20 ms

10 ms

30 ms

G.723 5.3 kbps

30 ms

30 ms

90 ms

G.723 6.3 kbps

30 ms

30 ms

90 ms

G.729

20 ms

10 ms

60 ms

G.729E/G (SIP ONLY)(10.3.2 ER2 and above)

20 ms

10 ms

30 ms

iLBC 20 ms

20 ms

20 ms

20 ms

iLBC 30 ms

30 ms

30 ms

30 ms

GSM-FR Static Payload Type

20 ms

20 ms

60 ms

GSM-FR Dynamic Payload Type

20 ms

20 ms

60 ms

G.726-32/G.721 Static Payload Type

20 ms

10 ms

60 ms

G.726-32/G.721 Dynamic Payload Type

20 ms

10 ms

60 ms

Clear Channel Codec

20 ms

10 ms

30 ms

Additional Information:

An IMG 1010 populated with Mindspeed VoIP modules does not support tone detection for any of the wireless codecs which includes the following:

  • AMR

  • EVRC

  • GSM-FR

  • GSM-EFR

  • Clear Channel

However, it is possible that an IMG with Mindspeed VoIP Module could pass a fax using wireless codecs to a Remote Gateway. In order for this to work, the Remote entity must send the IMG something to trigger it to switch to fax. Some examples would be:

  • Initiating T38 packets from their side -or-

  • Use the SIP REI (Re-Invite Message) process to update the T38 Port numbers so the signaling would drive the media layer to a fax state.

 

Return to Documentation Home I Return to Sangoma Support