[asterisk-bugs] [Asterisk 0011541]: SIP Redirect causes Asked to transmit frame type 64, while native formats is 0x4 (ulaw)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11541 
====================================================================== 
Reported By:                norman
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11541
Category:                   Channels/chan_sip/CodecHandling
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     confirmed
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-13-2007 15:30 CST
Last Modified:              01-30-2008 14:48 CST
====================================================================== 
Summary:                    SIP Redirect causes Asked to transmit frame type 64,
while native formats is 0x4 (ulaw)
Description: 
If I have an active call on client 1, then blind transfer that call to
client 2, then send a SIP 302 redirect of the call back to client 1, my
console fills up with "Asked to transmit frame type 64, while native
formats is 0x4 (ulaw)" messages. The ring tone cannot be heard by the
original caller as it normally is for transfers (i.e. the first transfer.)
Then after I hang up, I get these every few seconds:

Remote host can't match request BYE to call ... Giving up.

Except it doesn't give up, since they continue as long as the client is
registered.
====================================================================== 

---------------------------------------------------------------------- 
 norman - 01-30-08 14:48  
---------------------------------------------------------------------- 
I applied this patch to 1.4.17 and it did not correct the problem. I'm not
using MoH, BTW. It seems like it should send a ring indication in my case,
as it does if you answer then transfer. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-30-08 14:48  norman         Note Added: 0081459                          
======================================================================