Bayonne GnuComm

Driver-Specific Questions

• SIP Support using eXosip2 Library
  • Which Version of eXosip do I use with Bayonne 2?
  • How do I register my script with an authenticating proxy?
• Voicetronix Computer Telephony Drivers
  • What platforms does Voicetronix support?
  • Which driver releases should I use on GNU/Linux?
  • Why not use the new 3.0 driver?

Platform-Specific Questions

• Using GNU Bayonne 2 on Microsoft Windows
  • How do I use Bayonne 2 on Microsoft Windows?
  • How do I build from source on Microsoft Windows?
  • Why is Bayonne on Microsoft Windows built using Visual Studio 6?

Which Version of eXosip do I use with Bayonne 2?

We are currently using libeXosip2 2.2.2, which is the currently supported release of the eXosip library. Earlier versions of Bayonne 2 used the older libeXosip (1) library, but this is no longer supported.

How do I register my script with an authenticating proxy?

You will use the secret and user id of the proxy as part of your registration statement, for example:

 register.sip proxy=192.168.1.95 userid=290 secret=XXX timeout=60
 play &number 123
 sleep 500ms
 play &number 123
 exit
 ^2
 echo "interrupt"
 exit

What platforms does Voicetronix support?

Voicetronix is supported on GNU/Linux, some versions of FreeBSD, and Microsoft Windows. Only the GNU/Linux drivers support both the OpenSwitch and OpenLine cards.

Which driver releases should I use on GNU/Linux?

I suggest the 2.4.x release. The current one is 2.4.9. This builds on GNU/Linux, both on systems with 2.4 and 2.6 kernels. I would recommand using any late gcc3 (3.3 or 3.4) -based GNU/Linux distro such as CentOS-4.

Why not use the new 3.0 driver?

When it is ready, perhaps. I do not know if we will be supporting that release or the Voicetronix OpenPRI card, as it is a repackaged Sangoma card, and the libsangoma channelized voice interface offers less overhead. If we do not support OpenPRI directly, then the 2.4.x Voicetronix drivers should be fine for supporting their existing analog cards on Bayonne.

How do I use Bayonne 2 on Microsoft Windows?

The simplest way to accomplish this is to install the CAPE-xxx.exe runtime package. This includes the Common C++ components compiled under Visual Studio 6.0. You should not install CAPEXP, because Bayonne is normally compiled for VS 6 as well. You can then install one of the Bayonne-xxxx.exe distributions directly.

How do I build from source on Microsoft Windows?

You can rebuild Bayonne from source once you have CAPE installed. You will need Visual C++ 6.0 with SP6, and you will also need the Febuary 2003 release of the “Platform” SDK, which is the last release officially to support Visual C++ 6. This is needed because CAPE is compiled with IPV6 support. You could alternately rebuild the CAPE libraries from their various .dsp projects without IPV6 support and use much older Platform SDK's, but oSIP/eXosip also depends on the later platform SDK's.

Why is Bayonne on Microsoft Windows built using Visual Studio 6?

It may also be possible to build Bayonne with VS.NET and later versions of Visual Studio. If you do this, you will want to install the CAPEXP version of the cape runtime, which includes Common C++ libraries and oSIP compiled on VC 7. The dsp files may automatically import. We do not build Bayonne on later versions of Visual Studio because many of the telephony drivers we may wish to use in Bayonne on Microsoft Windows in the future are also only built from VC 6.