G729 codec AND ability to specify which codec MJ uses.
Moderators: Bill Smith, Pilot
G729 codec AND ability to specify which codec MJ uses.
I know MJ uses G711. Adding G729 would solve a LOT of people's bad call quality problems caused by slower or "high jitter" connections.
Does that use more CPU resources? I thought I read somewhere that it does. It would be good if MJ let you not only choose the codec, but also choose the CPU priority to give it.
I don't know if a process can set its own priority. But, that would be better than making people do it manually through task manager. (Even better than dead chat support telling people to go into "my computer" (properties) and giving priority to *all* background processes.).
Mark
I don't know if a process can set its own priority. But, that would be better than making people do it manually through task manager. (Even better than dead chat support telling people to go into "my computer" (properties) and giving priority to *all* background processes.).
Mark
I haven't looked to see which "alternative" CODEC(s) MJ now supports, but there is a clue in the FAQ that there is at least one low-bandwidth CODEC available.
The clue is in the FAQ entry that talks about using MJ on a dial-up internet service. The FAQ answer says that it is not possible for outbound calls, but that MJ-to-MJ calls may work.
The reason for this is, as with all things MJ, financial. Even though the MJ client is now capable of using a CODEC besides G.711, the MJ inbound origination and outbound termination providers only work with G.711 (presumably, to ensure the best voice quality). For MJ to allow your client to make and receive PSTN calls using G.729 or some other low-bandwidth CODEC, MJ would have to implement CODEC transcoding in their SIP server. That costs money -- money that we would ultimately pay in the form of higher pricing.
The clue is in the FAQ entry that talks about using MJ on a dial-up internet service. The FAQ answer says that it is not possible for outbound calls, but that MJ-to-MJ calls may work.
The reason for this is, as with all things MJ, financial. Even though the MJ client is now capable of using a CODEC besides G.711, the MJ inbound origination and outbound termination providers only work with G.711 (presumably, to ensure the best voice quality). For MJ to allow your client to make and receive PSTN calls using G.729 or some other low-bandwidth CODEC, MJ would have to implement CODEC transcoding in their SIP server. That costs money -- money that we would ultimately pay in the form of higher pricing.
Have been making G.729 calls, but not utilizing the MJ device as I am viloating my TOS shh dont tell.mberlant wrote:I haven't looked to see which "alternative" CODEC(s) MJ now supports, but there is a clue in the FAQ that there is at least one low-bandwidth CODEC available.
.
I am using my SIP creds configured as a SIP trunk on a Cisco IOS device.
UC520#sho sip calls
SIP UAC CALL INFO
Call 1
SIP Call ID : [email protected]
State of the call : STATE_RECD_PROCEEDING (4)
Substate of the call : SUBSTATE_NONE (0)
Calling Number : Exxxxxxxxxx1
Called Number : 1xxxxxxxxxx
Bit Flags : 0xC04018 0x100 0x4200
CC Call ID : 1159
Source IP Address (Sig ): X.X.X.X
Destn SIP Req Addr:Port : 67.88.10.198:5070
Destn SIP Resp Addr:Port: 67.88.10.198:5070
Destination Name : proxy1.cleveland.talk4free.com
Number of Media Streams : 1
Number of Active Streams: 1
RTP Fork Object : 0x0
Media Mode : flow-through
Media Stream 1
State of the stream : STREAM_ACTIVE
Stream Call ID : 1159
Stream Type : voice+dtmf (1)
Negotiated Codec : g729r8 (20 bytes) Codec Payload Type : 18
Negotiated Dtmf-relay : rtp-nte
Dtmf-relay Payload Type : 101
Media Source IP Addr:Port: X.X.X.X:17812
Media Dest IP Addr:Port : 67.88.10.203:20776
Orig Media Dest IP Addr:Port : 0.0.0.0:0