FXO PCI card configuration

[Luis Espinoza]

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.

[Todd Hodgen]

That configuration is not supported in sipXecs. You will have to have
external gateways.



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Luis Espinoza
Sent: Monday, June 18, 2012 11:34 AM
To: sipx-***@list.sipfoundry.org
Subject: [sipx-users] FXO PCI card configuration



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.

[Tony Graziano]

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...

Post by Luis Espinoza
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
sip: ***@voice.myitdepartment.net
Fax: [phone]
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

[Tony Graziano]

(historically, there was a gentoo build as late as version 3.8 but noone
has maintained it or shown any interest in doing so, that was about 5 years
ago. Just because there was a gentoo build "then" doesn't mean it will
compile now. Looking forward to sipx 4.6, it really ought to be determined
if the prerequisites for mongo and other new packages can be met easily
before anyone would think about pursuing it)

Post by Tony Graziano
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...

Post by Luis Espinoza
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
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
Fax: [phone]
~~~~~~~~~~~~~~~~~~
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
sip: ***@voice.myitdepartment.net
Fax: [phone]
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

[Kurt Albershardt]

As a system architect, I really like Gentoo. As a system administrator (after several years of use on many servers) it frustrated me -- eventually to the point where it drove me right off the bus.

Previous suboptimal experiences with Slackware and Red Hat had led me to Gentoo. Its "bleeding-edge is good" change management process eventually drove me to Debian. I inquired about sipx on Debian some years back and received 'less than hopeful' replies.

Over time, I have come to understand that distro biases are mostly about sysadmin tasks -- and the those mostly boil down to personal preference.

At this point, the overwhelming majority of the Linux world has coalesced around rpm and apt for package management. While I have my own preferences, I can hardly fault a development team with limited resources when it chooses to support only one of those models. Current (template-based) virtualization platforms are on the way to eliminating distros as anything other than a footnote regardless.



For the record, I prefer CentOS or Debian server platforms -- both embrace relatively conservative change management philosophies and have healthy bases of "big server" users.

(historically, there was a gentoo build as late as version 3.8 but noone has maintained it or shown any interest in doing so, that was about 5 years ago. Just because there was a gentoo build "then" doesn't mean it will compile now. Looking forward to sipx 4.6, it really ought to be determined if the prerequisites for mongo and other new packages can be met easily before anyone would think about pursuing it)
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.
I am currently developing a PBX, I decided to venture with sipXecs Gentos 4.4.

[Matt White]

Post by Kurt Albershardt
As a system architect, I really like Gentoo. As a system administrator (after several years of use on many servers) it frustrated me -- eventually to the point where it drove me right off the bus.
Previous suboptimal experiences with Slackware and Red Hat had led me to Gentoo. Its "bleeding-edge is good" change management process eventually drove me to Debian. I inquired about sipx on Debian some years back and received >'less than hopeful' replies.
Over time, I have come to understand that distro biases are mostly about sysadmin tasks -- and the those mostly boil down to personal preference.
At this point, the overwhelming majority of the Linux world has coalesced around rpm and apt for package management. While I have my own preferences, I can hardly fault a development team with limited resources when it chooses to >support only one of those models. Current (template-based) virtualization platforms are on the way to eliminating distros as anything other than a footnote regardless.
For the record, I prefer CentOS or Debian server platforms -- both embrace relatively conservative change management philosophies and have healthy bases of "big server" users.

I'd encourage you to take the dive and see if you can get a gentoo build stable. We build our own Suse builds and its the only thing we deploy. Sure, its a bit of work and you have to be prepared to do your own upgrade process. But for us its more than worth it. And with 4.6 around the corner, we've dodged a bullet because we can upgrade without the full reinstall like the centos builds ;-)

None of the deps are too difficult to build from source. And I think a wide diversity of distros helps widen the audience for sipx.

-M

[Douglas Hubler]

Post by Matt White
I'd encourage you to take the dive and see if you can get a gentoo build
stable.

I have a fondness for gentoo, so i'll try to answer questions and
review/accept patches quickly.