That would also require a driver for the OS and I think you would have better luck developing on CentOS since the build is known to work on that right now.
In the instance of gentoo, you would need to see if all of the prerequisites have a "gentoo" package available, then you will have to also make your own gentoo build (I am not sure anyone has built gentoo versions before), then you will have to write a plug-in for the modem configuration and another to communicate "with" the modem. Then you will be the only firm out there with gentoo and getting support would not exactly be easy with regard to sipx. I think it will be a lot of effort "needlessly" because you decide "gentoo" is what you want to run it on. Uou will find that you might need support from the modem manufacturer to fix any incompatibilities with the modem and sipx. This is a good reason why the POTS/TELCO gateways could and do remain an independent gateway. Patton makes ISDN gateways and are available in your part of the world and are already known to work with sipx. They also make FXO, FXS and PRI gateways available where you are. Realize sipx communicates with gateways via their IP address. You change a lot when you want to channel that gateway to an internal device. It's not been done before. It also removes a lot of scalability in sipx. Using an external gateway, you can establish a PSTN call between a user and a PSTN caller and disconnect the sipx system from the network without interrupting the call in progress. What you are asking, and probably without realizing it, is to rewrite the underlying distributed architecture of the product to support a modem. Using the existing builds and a supported or known gateway means you can start supporting sipx now... On Mon, Jun 18, 2012 at 2:34 PM, Luis Espinoza <[email protected]>wrote: > Hi.. > > I am currently developing a PBX, I decided to venture with sipXecs Gentos > 4.4. > > I need to implement the local telephone line (traditional) to the PBX, I > have a PCI card "Tiger Jet NetworkInc. Tiger3XX Modem / ISDN interface". It > has 4 slots for chips, but only contains one FXO type. > > The first thing I understood about this issue is that I configure the > Gateways section, which is able to determine sipXecs some and not others. > Among the list of those recognized sipXecs closer is "AudioCodes MP 114 > FXO" but the configuration panel asks me "IP Address" and "Serial or MAC > address" and at this point not to enter because it is a PCI card not > external, is on the same PC that hosts sipXecs. > > I need help to implement the traditional phone line sipXecs. Thanks in > advance and excuse my bad English. > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
