Summary:ASTERISK-11030: SIP Redirect causes Asked to transmit frame type 64, while native formats is 0x4 (ulaw)
Reporter:Norman Franke (norman)Labels:
Date Opened:2007-12-13 15:30:14.000-0600Date Closed:2008-08-04 17:45:49
Versions:Frequency of
Environment:Attachments:( 0) 11541-sb.diff
( 1) sip.log
( 2) sip.out
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.
Comments:By: Joshua C. Colp (jcolp) 2007-12-13 15:31:00.000-0600

We need the full console output with sip debug to look at this.

By: Norman Franke (norman) 2007-12-13 15:37:19.000-0600

I've just uploaded the log. It timed out the first time I tried, but the second upload worked OK.

By: Norman Franke (norman) 2007-12-13 15:45:18.000-0600

This is from a non-production system, so if you need any additional information, just let me know.

SIP/station09 makes a call to 221 (an internal hard phone on our PBX via a Cisco gateway.)
SIP/station09 transfers to SIP/station10 which then redirects it back to SIP/station09.

The "stationxx" are softphone clients (based on PJSIP, if that helps/matters.)

By: Norman Franke (norman) 2008-01-10 10:21:48.000-0600

Any word on this? It continues to happen and fills up the console log with warnings:

[Jan 10 06:21:26] WARNING[24779]: chan_sip.c:3634 sip_write: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)

Like 20 per second.

By: Sean Bright (seanbright) 2008-01-30 10:00:56.000-0600

Confirmed in 1.4.18 rc2 doing the following:

One eyeBeam has two registrations, A and B.  A calls B.  B answers.  I then see the same errors as above:

[Jan 30 11:03:07] WARNING[24682]: chan_sip.c:3668 sip_write: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)

By: Sean Bright (seanbright) 2008-01-30 10:11:45.000-0600

Uploaded sip.log

This is what is happening from a single eyeBeam client (2 registrations on the same client):

 Registration 1 (CHX_1442) calls Registration 2 (CHX_1444), Registration 2 (CHX_1444) answers, Registration 2 (CHX_1444) hangs up.

By: Norman Franke (norman) 2008-01-30 14:48:22.000-0600

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.

By: Tilghman Lesher (tilghman) 2008-08-01 14:13:29

What phones do you have and how did you set this up?  I am trying with the latest 1.4 SVN, and I cannot reproduce this error with two Polycom phones, one forwarded to the other.

By: Norman Franke (norman) 2008-08-04 15:45:22

I'm using PJSIP, a soft client. I'm now using and it does not appear to happen anymore. Perhaps something got fixed between 17 and 21?

By: Tilghman Lesher (tilghman) 2008-08-04 17:45:47

Unable to reproduce in latest SVN.