The patton will allow a phone to register to it directly as a secondary line. You can bypass the sipx proxy altogether from that phone. Inbound calls would work also. ============================ 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] <[email protected]> Cc: [email protected] users <[email protected]> Sent: Sat Feb 06 16:44:39 2010 Subject: Re: [sipx-users] Single port FXO - outbound only The spa3102 is "fine" for outbound calls and its certainly cheap. It also has a failover relay so you can have an analog phone plugged into the fxs side and if the power goes out it will bridge the fxo to the fxs. All the (many and ultimately fatal) problems I had were related to malformed headers causing trouble on inbound call (things going thru the AA). I also never got it to detect CPC inbound so I had to build a little DSP 'busy tone' detection string that matched the PBX FXS line I was testing with. It didn't detect CPC from raw telco either but the default north america busy signal detection did work (you would just get 2 seconds of busy signal at the end of every voicemail). You do have to be careful about DTMF signalling, it hardcodes the RTP code for telephony events as 101 (if I recall) and the default polycom/sipx config ends up trying to use 127 -- the SPA allows the negotiation but then just doesn't send DTMF. Also, in the outbound direction: getting it to recognize the idle loop voltage from a PBX I was testing with required configuration. The pbx only put out 24V when idle and by default that wasn't enough to make the SPA3102 think there was an FXS present (but there's a configuration setting for that). The debugging (via syslog only) is very rudimentary but better than nothing. Despite being unsupported by Cisco and non-SIP standard compliant (broken at the protocol level) it was stable for the 3 months I was testing with it (never crashed or did anything flakey). If I had your requirement ("outbound calls, emergency line, cheap") the SPA3102 seems pretty appropriate. -Eric On Feb 6, 2010, at 1:51 PM, [email protected] wrote: > Anyone have a single port FXO they like? It is for emergency outbound > calls only. No inbound. I'm familair with the products from Audiocodes > and Patton, but I would love to find a cheaper single port option if > there is one out there that is compatible with sipx. From what I have > read, I'm assuming none of the actual PCI card options are compatible > with sipx. That would be really cool if there was one that would work. > I'm going for simplicity and affordability. The spa3102 is cheap, but I > don't seem to find much in the way of success stories with it and sipx. > Any tips would be greatly appreciated. > > Thanks, > Matthew > _______________________________________________ > 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/ _______________________________________________ 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/
