> Back up... you didn't tell us anything about what was happening. Who > called what? Did what? What should have happened? What did happen? > Sorry, I probably should have put the 'physically what happened' block at the TOP of the email instead of the middle. Mea culpa.
> "incoming call from fxo2 (Patton smartnode) goes to '0' on the AA, I type > '200' and it transfers to user called 'Kitchen' (I need better phone names :) > ), it rings there a couple of times and I hit 'Reject' then immediately (on > the onbound FXO line) hear fast busy" I should have added "I expected a ringing user hitting Reject on the phone would send the calling party to voicemail or back to the AA (as I remember it working in 4.0.4)". > I'm going to guess (based on the trace) that someone called in from the > outside, landed on an auto-attendant, and did something that should have > transferred them to extension 200. Extension 200 rejected the call, but > does not have voicemail. The call was dropped. Right? The user was the first set up from a fresh install (--first-run) with defaults and I expected it to have voicemail based on my experiences with 4.0.4. Thank you! The user does not have voice mail, I never thought of checking if voicemail was enabled. On the user permissions screen voice mail is unchecked and it says 'default unchecked'. I actually like this default better than on 4.0.4, it was just unexpected. I did a bit of experimenting just now and: - If the called user has voicemail permission added REJECT stops the phone (650) ringing but the caller on the FXO side is not connected to voice mail until the 'ring no answer' timeout which is defaulted. On 4.0.4 with the 3.1.3 firmware on this phone pressing REJECT sent the call immediately to voice mail (which seems better). At least I can look at a trace where it went to voicemail on its own and try to figure out all this is supposed to work with the Autoattendant code now. - If the called user is "shared" no REJECT button shows up at all (instead the 3.2.2 firmware puts up 'answer', 'silence', and 'new call'). Silence acts like 'REJECT' on the non-shared user, the calling user on the FXO gets no change in audio signalling and waits for the no-answer timeout then falls into voice mail. Thanks for the help! -Eric > > If so, that's exactly what you told it to do. > > The AA does not attempt to recover a failed blind transfer. > > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
