On Feb 9, 2010, at 9:32 AM, Dale Worley wrote: [...] > Looking at the traces, I see that 5907 receives a REFER to 5903, and > then generates an INVITE to 5903. What I don't see is any attempt by > 5907 to CANCEL that INVITE after (as you say) 5907 is hung up. So it > looks like the originating phone (snom870/8.4.1) isn't handing a hangup > correctly while it is executing the REFER.
You are right Snom 8.4.1 didn't issue CANCEL after REFER. I am not sure if I posted the other set of logs with the older Snom 8.3.7. That older firmware clearly sends the CANCEL. So I have filed a trouble ticket with Snom and sent them all the log files. [...] > > In both cases, the actual execution of the transfer is done by the UA > that remains in the call. In this case, it's sipXbridge. While > sipXbridge is executing the REFER that implements the (presumably blind) > transfer, if its other side terminates, sipXbridge should cancel the > INVITE that it has generated for the REFER. [...] That's right. No CANCEL from sipxbridge after REFER. Per Ranga's suggestion, I'll try the main build and see if the problem is reproducible. Thanks for the help, Dale and Ranga. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
