[Home]

Summary:ASTERISK-17742: ulaw/g722 Transcode Issue
Reporter:ewieling (ewieling)Labels:
Date Opened:2011-04-22 08:00:54Date Closed:2017-12-19 06:55:00.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:1.8.3 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) asteriskfull-2011-08-22.txt
( 1) sip.cap.txt
( 2) sip-2011-08-22.conf
( 3) sip-user-2011-08-22.conf
Description:
Something seems broken with transcoding.  1.8.3 and 1.8.4-rc2

[2011-04-21 09:51:34] WARNING[22067]: chan_sip.c:6064 sip_write: Asked to transmit frame type ulaw, while native formats is 0x1000 (g722) read/write = 0x1000 (g722)/0x1000 (g722)
[2011-04-21 09:51:34] WARNING[22067]: chan_sip.c:6064 sip_write: Asked to transmit frame type ulaw, while native formats is 0x1000 (g722) read/write = 0x1000 (g722)/0x1000 (g722)
[2011-04-21 09:51:34] WARNING[22067]: chan_sip.c:6064 sip_write: Asked to transmit frame type ulaw, while native formats is 0x1000 (g722) read/write = 0x1000 (g722)/0x1000 (g722)
[2011-04-21 09:51:35] WARNING[22067]: chan_sip.c:6064 sip_write: Asked to transmit frame type ulaw, while native formats is 0x1000 (g722) read/write = 0x1000 (g722)/0x1000 (g722)
[2011-04-21 09:51:35] WARNING[22067]: chan_sip.c:6064 sip_write: Asked to transmit frame type ulaw, while native formats is 0x1000 (g722) read/write = 0x1000 (g722)/0x1000 (g722)
Comments:By: Leif Madsen (lmadsen) 2011-04-26 08:16:38

This isn't a transcode problem really, it's a bug in that asterisk is feeding chan_sip one format while it expects another.

To move this issue forward we need to figure out how the call got into that state.

Console log, some description of what is going on with the call that gets into this state, and a SIP trace (if using SIP) will be required.

By: ewieling (ewieling) 2011-04-26 08:20:33

I will see what I can do.  This is a production box, any logs will be very cluttered.

By: Arkadiusz Malka (yarns) 2011-05-04 04:43:22

Isn't this related to: https://issues.asterisk.org/view.php?id=18916 ?

By: ewieling (ewieling) 2011-05-04 07:50:49

I don't know if it is related, but directmedia=no does not solve the issue.

By: Hugh Riley (hughriley) 2011-08-22 11:20:18.732-0500

I was seeing the same thing when dialing a user with FollowMe enabled. Turns out, he had "disallow=all,allow=g722" in his SIP record. Removing that cleared it up. However, from what I can see it should have transcoded, but didn't. I'll attached pertinent files.

By: Hugh Riley (hughriley) 2011-08-22 11:21:34.724-0500

Files related to transcode issue mentioned above.

By: Luke H (luckman212) 2012-01-20 00:34:57.278-0600

Is this still an issue?  Was this ever confirmed as a bug, or was it a config error?  I've seen these "Asked to transmit frame type ulaw, while native formats is 0x1000 (g722) read/write = 0x1000 (g722)/0x1000 (g722)" messages as well, so I'm interested to hear any followup.

By: Joshua C. Colp (jcolp) 2017-12-19 06:55:01.075-0600

I believe that the underlying cause of this was fixed a few years ago when things were changed to redo the translation path.