On Mon, 2010-01-25 at 10:01 -0600, Eric Varsanyi wrote: > I've replaced my FXOs with Patton smartnodes (which so far I > absolutely love from a configurability and debugablity point of view). > After hitting 'Reject' on an AA transferred call to a Polycom 650 I > get a fast busy on the FXO. Previously it was going fast busy because > Freeswitch was crashing on the malformed headers from the SPA3102 FXO, > now it appears to be something else.
Ignore the noises <insert rant="futility of noises in SIP debugging"/> > From my lame (but improving) reading of the call trace it looks like > the Polycom sends a 'Busy Here' when I hit the Reject key, then the > patton reflects that back to Freeswitch which is then told to hang up > by sipxivr and responds with a BYE rather than going back to the AA or > voice mail. Back up... you didn't tell us anything about what was happening. Who called what? Did what? What should have happened? What did happen? 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? 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/
