[asterisk-users] Help - call recording being cut short if transferred

[Julian Lyndon-Smith]

Thanks for the reply, but as I mentioned in the original email (option 
C), the /n causes problems with warnings on the console.

Julian (L. S.) :)

Julian J. M. wrote:
> Add /n to you Local dial string, i.e.:
> 
> Dial(Local/1234/n)
> 
>> From 
>> http://www.voip-info.org/wiki/index.php?page=Asterisk+Local+channels :
> 
> Adding "/n" at the end of the string will make the Local channel not
> do a native transfer (the "n" stands for "n"o release) upon the remote
> end answering the line. This is an esoteric, but important feature if
> you expect the Local channel to handle calls exactly like a normal
> channel. If you do not have the "no release" feature set, then as soon
> as the destination (inside of the Local channel) answers the line, the
> variables and dial plan will revert back to that of the original call,
> and the Local channel will become a zombie and be removed from the
> active channels list. This is desirable in some circumstances, but can
> result in unexpected dialplan behavior if you are doing fancy things
> with variables in your call handling.
> 
> 
> 
> Julian J. M.
> 
> On 8/5/06, Julian Lyndon-Smith <asterisk at dotr.com> wrote:
>> Using svn trunk, I am trying to record a call coming in from a zap line.
>>
>> This works:
>>
>> A) Zap->StartRecording->DialSip->xferToSIP2->Talk->Hangup
>>
>> The entire call is recorded until the hangup
>>
>> However, if you use a local channel instead:
>>
>> B) Zap->StartRecording->DialLocal->DialSip->xferToSIP2->Talk->Hangup
>>
>> the conversation is recorded up to the xferToSip2 part (i.e. the
>> conversation between Zap and SIP2 is not recorded)
>>
>> If I add /n to the local channel
>>
>> C) Zap->StartRecording->DialLocal/n->DialSip->xferToSIP2->Talk->Hangup
>>
>> The entire call is recorded until the hangup, BUT the call quality is
>> extremely poor, and I get a whole heap of warnings on the console (see
>> below).
>>
>> Why does B) not work ? I would have thought that recording the zap
>> channel would continue *until* the zap channel hung up, regardless of
>> what goes on with the other channels.
>>
>> Any light on this would be most appreciated. I've got my *ss kicked for
>> this (we do a lot of transfers) and I've been told to "sort it" for this
>> weekend ;(
>>
>> Julian
>>
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>> [Aug  5 09:07:28] WARNING[26717]: chan_sip.c:3342 sip_write: Asked to
>> transmit frame type 8, while native formats is 4 (read/write = 8/4)
>>
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
> 
>