I am having a problem with the tranfer function since changing our t1 to PRI. I used to be able to answer a forwarded call to my cell phone, then transfer the call back using ## (we have it set to ## in features.conf). Since the update it does not work most of the time. At lunch today I had a call and could not get it to transfer. The logs show asterisk getting the DTMF #, then a bunch of stuff about a zap channel not being answered yet. I see two #'s coming in withing the time configured in features.conf but being ignored. It looks like the original call came in on Zap2-1 and asterisk called my cell phone on Zap3-1 and bridged the calls but still thinks Zap2-1 is still dialing and ignores my dtmf even though I am on Zap3-1. Here are a few lines from the log: Jan 25 11:29:20 DEBUG[1131] chan_zap.c: DTMF digit: # on Zap/3-1 Jan 25 11:29:20 DEBUG[1131] chan_zap.c: Dropping frame since I'm still dialing on Zap/2-1... Jan 25 11:29:20 DEBUG[1131] chan_zap.c: Dropping frame since I'm still dialing on Zap/2-1... Jan 25 11:29:20 DEBUG[1131] chan_zap.c: Dropping frame since I'm still dialing on Zap/2-1... Jan 25 11:29:20 DEBUG[1131] chan_zap.c: Dropping frame since I'm still dialing on Zap/2-1... Jan 25 11:29:20 DEBUG[1131] chan_zap.c: Dropping frame since I'm still dialing on Zap/2-1... Jan 25 11:29:20 DEBUG[1131] chan_zap.c: Dropping frame since I'm still dialing on Zap/2-1... Jan 25 11:29:20 DEBUG[1131] chan_zap.c: Dropping frame since I'm still dialing on Zap/2-1... Jan 25 11:29:21 DEBUG[1131] chan_zap.c: Dropping frame since I'm still dialing on Zap/2-1... Jan 25 11:29:21 DEBUG[1131] chan_zap.c: Dropping frame since I'm still dialing on Zap/2-1... Jan 25 11:29:21 DEBUG[1131] chan_zap.c: Exception on 13, channel 2 Jan 25 11:29:21 DEBUG[1131] chan_zap.c: Got event Dial Complete(9) on channel 2(index 0) Jan 25 11:29:21 DEBUG[1131] chan_zap.c: Echo cancellation already on Jan 25 11:29:24 DEBUG[1131] chan_zap.c: DTMF digit: # on Zap/3-1 Anything I can check? This is CVS head as of end of last year. Thanks, James Armstrong