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.

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.

This is sipx @ SVN 17748 (approx 1/20) and Freeswitch is at SVN 16425 (also 
about 1/20) running on FC12 with Polycom 650's and 335's at 3.2.2.

A hint on how it *should* work in sipXivr (should there be a 'next' attendant 
when it goes to transfer()? is something else supposed to catch the 'bye' later 
on and redirect it to voicemail?) and I'll be set to debug further.

Apologies if this is really 'user' traffic, I will post there if so.

Thanks,
-Eric Varsanyi

Details:

Merged.xml of the whole conversation: 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.

Attachment: merged_xml.tar.bz2
Description: BZip2 compressed data

  (weird packaging to bypass my ISPs virus filter, sorry)

There are no obvious errors in the freeswitch log, the sipxivr log shows the 
'deflect' sending the call to the phone then when it comes back it decides to 
hang up (excerpt below). Looking at Attendant.java in sipxivr it appears to 
break out of the attendant loop after the (synchronous) transfer() call. Since 
transfer to extension did not set the nextAttendant var it sort of makes sense 
that its hanging up -- but I'm sure I'm missing the bigger picture since it 
didn't use to do this in 4.1.x code I checked out in early December and the 
last change in this area was in Oct according to svn.

bf9e""2010-01-25T14:39:26.956000Z":170:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSESI::invoke
 handler add org.sipfoundry.commons.freeswitch.trans...@1c
5fde0""2010-01-25T14:39:26.958000Z":171:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSES::cmd
 sendmsg\ncall-command: execute\nexecute-app-name: deflect\nex
ecute-app-arg: 
\"Kitchen\"<sip:[email protected]>""2010-01-25T14:39:26.961000Z":172:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSES::awaitEvent
 live response (command/reply) Event-Name ((null))"
"2010-01-25T14:39:26.968000Z":173:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSEII::invoke
 Send event((unknown)) to (org.sipfoundry.commons.freeswitch.trans...@1c5fde0)"
"2010-01-25T14:39:26.980000Z":174:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSES::awaitEvent
 live response (text/event-plain) Event-Name (CHANNEL_E
XECUTE)""2010-01-25T14:39:26.995000Z":175:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSEII::invoke
 Send event(CHANNEL_EXECUTE) to (org.sipfoundry.commons.fr
eeswitch.trans...@1c5fde0)""2010-01-25T14:39:34.292000Z":176:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSES::awaitEvent
 live response (text/event-plain) Event-Name (CHANNEL_E
XECUTE_COMPLETE)""2010-01-25T14:39:34.294000Z":177:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:
sipxivr:"FSEII::invoke Send event(CHANNEL_EXECUTE_COMPLETE) to 
(org.sipfoundry.commons.freeswitch.trans...@1c5fde0)""2010-01-25T14:39:34.296000Z":178:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSESI::invoke
 handler remove org.sipfoundry.commons.freeswitch.trans...@1c5fde0"
"2010-01-25T14:39:34.297000Z":179:sipXivr:INFO:pbx.foo21.com:Thread-4:00000000:sipxivr:"Attendant::attendant
 Ending attendant Operator"
"2010-01-25T14:39:34.299000Z":180:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSESI::invoke
 handler add org.sipfoundry.commons.freeswitch.han...@16c163f"
"2010-01-25T14:39:34.299000Z":181:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSES::cmd
 sendmsg\ncall-command: execute\nexecute-app-name: hangup"
"2010-01-25T14:39:34.303000Z":182:sipXivr:DEBUG:pbx.foo21.com:Thread-4:00000000:sipxivr:"FSES::awaitEvent
 live response (command/reply) Event-Name ((null))"

_______________________________________________
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/

Reply via email to