[Home]

Summary:ASTERISK-01560: notransfer=yes does not appear to work
Reporter:richard (richard)Labels:
Date Opened:2004-05-07 19:44:14Date Closed:2004-09-25 02:46:02
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Apologies if this is a mis-configuration, but I do not think so.

Setup:

Firefly soft IAX client ->(IAX2)-> asterisk-pbxwn ->(IAX2)-> asterisk-pbxak

In order to take advantage of IAX2 trunking between the 2 asterisks, I have added "notransfer=yes" to pbxwn's iax.conf, but pbxwn still attempts to transfer the firefly call directly to pbxak.

This occurs whether notransfer=yes is added globally or just to the firefly entry ([test] in the iax.conf below).


****** ADDITIONAL INFORMATION ******

pbxwn iax.conf

[general]
static=yes
[general]
;port=5036
;jitterbuffer=no
amaflags=default

bandwidth=high
disallow=lpc10
;disallow=all
;allow=gsm

context=iax

tos=lowdelay

notransfer=yes

[pbxak]
host=192.168.3.223
type=friend
context=default
trunk=yes

[test]
host=dynamic
type=friend
context=firefly
trunk=yes


pbxwn CLI

   -- Registered 'test' (UNAUTHENTICATED) at 192.168.4.24:4569
   -- Accepting unauthenticated call from 192.168.4.24, requested format = 4, actual format = 4
   -- Executing Dial("IAX2[test@test]/16384", "IAX2/192.168.3.223/555") in new stack
   -- Called 192.168.3.223/555
   -- Call accepted by 192.168.3.223 (format ULAW)
   -- Format for call is ULAW
   -- IAX2[pbxak]/2 answered IAX2[test@test]/16384
   -- Attempting native bridge of IAX2[test@test]/16384 and IAX2[pbxak]/2
   -- Channel 'IAX2[test@test]/16384' ready to transfer
   -- Channel 'IAX2[pbxak]/2' ready to transfer
   -- Releasing IAX2[pbxak]/2 and IAX2[test@test]/16384
   -- Hungup 'IAX2[pbxak]/2'
 == Spawn extension (firefly, 555, 1) exited non-zero on 'IAX2[test@test]/16384'
   -- Hungup 'IAX2[test@test]/16384'
Comments:By: richard (richard) 2004-05-07 19:56:46

Sorry, asterisk version CVS-HEAD-05/03/04-08:19:31
By: Brian West (bkw918) 2004-05-07 20:06:33

Sorry firefly doesn't support transfer in this manner.(well it might try)

I just did this:

PBX1 -> PBX2 -> PBX3

I called from PBX1 thru PBX2 to PBX3 with notransfer=yes along the way it worked as expected call was not released so the path stayed 1->2->3.  Commented the notransfer=yes out totally and it worked as expected path changed from 1->3.

This is not a bug.

edited on: 05-07-04 19:03
By: Brian West (bkw918) 2004-05-07 20:08:42

you need to have notransfer=yes on pbxak also.
By: richard (richard) 2004-05-07 20:14:28

It was included globally on pbxak and both asterisk's were restarted after the configs were changed.

Do I need an entry for [test] on pbxak with notransfer=yes included?

Re. your comment " Sorry firefly doesn't support transfer in this manner.(well it might try), do you mean what I am trying to attempt won't work or having the firefly call transfered directly to pbxak does not work?

If the latter, no it doesn't seem to.

edited on: 05-07-04 19:17
By: Brian West (bkw918) 2004-05-07 20:22:00

yes
By: richard (richard) 2004-05-07 22:58:00

Thanks for your help Brian.
By: twisted (twisted) 2004-05-08 00:29:36

Richard, should we consider this resolved now?
By: sbingner (sbingner) 2004-05-08 01:08:46

If an IAX client CAN actually perform a native transfer even when notransfer=yes is in the PBX's iax.conf, this seems like a bug to me.  When notransfer=yes is enabled, there should be no way for the client's audio to get off of that server....  also if it requires notransfer=yes on both servers, that is also a problem; you shouldn't need to rely on somebody else's config to ensure that you control the call that passes through you.

Unless I misunderstood something?
By: richard (richard) 2004-05-08 02:01:40

I am a little confused still, but as nobody else seems to seeing the problem, I am putting it down to either the behaviour of Firefly or some mistake on my part.

The last thing I tried was to add the same [test] entry to the pbxak, with a different context and notransfer=yes was added in each [test] config.

I still got a message on pbxwn saying it is transfering the call to pbxak.
By: richard (richard) 2004-05-08 03:08:37

Please take the last note as possibly incorrect. I wrote it from memory as I am away from the system. It may be that I have confused "transfering" with "native transfer" in this last case.

I will post again in 36 hours or so and include output.

If anyone can see anything wrong in my last described config, please let me know.

Thanks.

edited on: 05-08-04 02:04

edited on: 05-08-04 02:40
By: Mark Spencer (markster) 2004-05-08 10:30:41

It can't be a firefly problem.  "notransfer" was not a global option in chan_iax2, but I've updated cvs head to make it so, so your use of "notransfer" in the general section should now apply.
By: richard (richard) 2004-05-09 15:47:40

Everything seems to be working as advertised, except as noted by Brian above, Firefly will not transfer in this scenario, but as far as asterisk is concerned, the call is correctly set up.

My confusion was in thinking I did not need a [test] entry on pbxak, because I was assuming pbxwn would proxy firefly's call when notransfer=yes is used and use the [pbxwn] entry.

Thanks and we can call this resolved.
By: Mark Spencer (markster) 2004-05-09 21:37:28

Fixed in CVS