OK, poked around with traces from the patton itself as well as the normal sipx style tracing.
There's a trace in this merged XML (unfiltered): http://www.eljv.com/pub/merged_2010_0713t1.xml.gz , the scenario is: 1) Frame 79: Polycom 335 ([email protected], 10.0.1.15) calls patton FXS ([email protected], 10.0.1.4), set up goes normally and I'm talking at frame 107. 2) Frame 178: I hit 'flash' on the FXS extension, it does a re-invite to the 335 its talking to (why? I haven't dialed yet...?) 3) Frame 226: I dial '200' on the FXS and it issues an INVITE to a polycom 650 (10.0.1.12); all seems to go well and the FXS extension is talking to 200 by frame 267 4) Frame 310: I hang up the FXS and some sort of loop starts, the display on the 650 blinks every second or so as it processes the messages. The loop looks kind of like the FXS patton is telling each of the 335 and 650 to INVITE to themselves alternately (wtf?). Likely I'm just misreading some subtlety though. 5) This chatter goes on until I hang up the 650 around frame 610 at which point the chatter comes to a halt. -Eric On Jul 12, 2010, at 6:33 PM, Tony Graziano wrote: > I've never done this with an fxs port. The queatuion I have is when you do a > trnasger initiated from an fxs device, how do you know it is referred or > blind? > > A trace would be helpful. > ============================ > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > ----- Original Message ----- > From: [email protected] > <[email protected]> > To: [email protected] users <[email protected]> > Sent: Mon Jul 12 19:29:12 2010 > Subject: [sipx-users] Actual call transfer, should it work? (polycom -> > patton) > > [see the bottom for versions] > > When I receive a call on a subscribed FXS line on a patton 4114 I can flash > and make a 2nd call. The patton manual states that if I then hang up on the > second call the first call should 'transfer' to the destination. I've been > unable to make this work between FXS ports on the same patton and between a > patton fxs and polycom 650's. I flash, get dialtone, call another extension > and talk to it normally, but when I hang up the original caller hears only > silence and isn't disconnected. > > This fails the same if the call is from a patton FXO gateway (another box), > another FXS port on the same 4114, or from sipxbridge (voip.ms), or from a > Polycom phone. I've tried with the target being a polycom or another FXS on > the 4114. > > I do have the 'call-transfer' option enabled on the FXS interface in the > patton. > > The polycoms do 'referred' and 'blind' transfer as expected in all the above > scenarios (call from patton FXS, FXO, ITSP/sipxbridge, or another polycom). > > I will run traces next, just curious if normal call transfer has ever been > known to work with Patton FXS ports or am I just wasting my time? > > This is sipxecs 4.2. > Polycom: 0711224145|app1 |3|00|Application, load: Type=SIP, > Version=3.2.3.1734 22-Mar-10 15:56 > Patton fxo+fxs: Software Version : R5.4 2009-11-18 H323 SIP FXS FXO > > Thanks, > -Eric > _______________________________________________ > 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/ _______________________________________________ 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/
