The Patton manual is delightfully vague on this... from the description it sounds like referred (you have to have the '2nd' call up and running). I did try dialing and hanging up before the target extension answered and that didn't change anything, so I suspect it can work either way (just like my old panasonic switch or the telco feature) if it works at all.
Here's what little they have to say FWIW: Call transfer The call transfer feature is only available if the second call was originated by the local subscriber. For execution, the local subscriber goes on-hook and the active call and the held call will be transferred together. If the second call was an incoming call, the active call will be dropped and the CWRR will appear to signal a pending hold call. It is possible to disable this service by executing the command no call-transfer on the fxs interface. Mode: Interface FXS 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/
