Bayonne, telephony server of GNU project

I had the libxml problem myself.  Adding the check would be nice.  The
root of the problem, however, is documentation.  At this point,
someone who downloads the bayonne sources from, say, gnu.org or
voxilla.org, and then reads the bayonne README, and INSTALL, and
BAYONNE.FAQ, and the manual, will still have fair bit of guesswork
ahead of them before getting anything running.  In particular,
bayonne-0.6.4 is a long way from the README's "drivers installed
... ./configure ... make ... cd server ... ./bayonne --test".
Particulary for those who do not have the vpb stuff, embedded perl,
and libxml installed. Ideally, one should be able to download a
Bayonne tarball, read the README, and continue without guesswork.

I suggest a few mods to the README and the INSTALL file that will
require maintenance.  I think this will minimally bring 0.6.5 within
the guesswork threshold of the average programmer.  This in no way
replaces the manual, but provides a mechanism for making the simple
build documentation changes required on a release basis to keep
guesswork out of the current tree.  I would be happy to test releases
on the development tree locally and update these two files with a
little notice.

I threw the modded README and INSTALL files on
ftp.voxilla.org:/home/pub/incoming/

-Rich

> To support more easily building and testing Bayonne either with or without XML
> support in Common C++, the next release (0.6.5) will test for the new
> "COMMON_XML_PARSING" directive, which I have added as a conditional directive
> in Common C++ 1.5.1.  This should clear up any confusion for those that do not
> have libxml2 installed when they build Common C++ and then try to run Bayonne
> in "test" mode...
>

> I threw the modded README and INSTALL files on
> ftp.voxilla.org:/home/pub/incoming/

Correction: ftp.voxilla.org:/pub/incoming/

And I fixed the README.

-Rich

Rich Bodo | rsb@... | 650-964-4678

Well,

	I currently use yesterdays closing stock price of a publicly
	traded company plus a portion of the time as a one-time
	voicemail password. I have a Kyocera-Palm phone now, and would
	like to have one of those cool one-time password generator
	programs like the credit-card sized wallet thingies running on
	it.  I don't even know how they work, but as long as I've got
	the processing power...can't wait to hack the phone features
	of this Kyocera.

-Rich

> hello,
> i am a developer in a small company in Mumbai, India.
> We develop applications for the wireless devices such
> as palm, mobile phones etc.
> We are planning to develop some applications on voice
> xml. could you suggest some applications on it so that
> we could explore more possibilities
> regards,
> swapnil

Rich Bodo | rsb@... | 650-964-4678

I have been away much of the last few weeks and haven't really had a chance to 
look into this yet...

David

Abraham Ingersoll wrote:

> No one ever acknowledged this post to the list last month, and I'm seeing
> the same minor issues under bayonne 0.64 with ccscript 1.6.1.
> 
> Is this in fact a bug, or should I shut up, learn some more c++, and only
> pipe up again after next semester? :)
> 
> Abe
> 
> ---------- Forwarded message ----------
> Date: Fri, 29 Jun 2001 11:48:36 -0700 (PDT)
> From: Abraham Ingersoll <abe@...>
> To: Bayonne-devel@...
> Cc: David Sugar <dyfet@...>
> Subject: [Bayonne-devel]ccscript bugs
> 
> 
> When I add debugging output within ScriptInterp::Conditional that prints
> out the two values and the operator (v1, op & v2) from an in-progress
> ccscript, it seems that the operators '$' and '=' aren't properly passed
> to the Conditional method. -eq, .eq., etc works, but anything starting
> with = or $ is either slipping past by debug output, or just isn't
> working because it gets caught somewhere before Conditional.
> 
> This is the line I used for debugging output:
> 
> slog(SLOG_INFO) << "Conditional: v1=" << v1 << " op=" << op << " v2=" << v2 << endl;
> 
> Here's a snip from what bayonne shows when -T and -F'd:
> 
> vpb0: step 3 if(%var1,=,%abe,::abe)
> Conditional: v1=%var1 op=::abe v2=(null)
> 
> vpb0: step 3 if(%var1,,%abe,::abe)
> Conditional: v1=%var1 op= v2=%abe
> 
> The relevent bits from the ccscript that I'm using the test this:
> 
> set %var1 %session.digits
> init %abe 223
> if %var1 $ %abe ::abe
> 
> And
> 
> set %var1 %session.digits
> init %abe 223
> if %var1 = %abe ::abe
> 
> Btw, this is all under ccscript 1.6.0, but from a quick glance, it doesn't
> look like anything's changed in regards to this in 1.6.1.
> 
> Abe
> 
> 
> 
> _______________________________________________
> Bayonne-devel mailing list
> Bayonne-devel@...
> http://lists.sourceforge.net/lists/listinfo/bayonne-devel

> I've written a few scripts, read the manual, and got a general feel for the
> scripting language, and a few other bits of information, but for the life of
> me cant work out how to actually have bayonne run the scripts... how do i do
> this?

Call in.  Do you have a way to grab a channel on the E1?  A channel
bank or a switch of some sort?  Alternately, on the command line you
can use something like:

bayctrl start 1 myscript

I'm kind of curious about the ISDN DNIS question myself.

-Rich

Rich Bodo | rsb@... | 650-964-4678

Cleaning up aqnd testing digital card support was what I was going to focus on 
when I get back later this week.  If you are using PRI spans with DNIS 
service, no, it will not work at all currently because it doesnt initialize 
the ISDN firmware.  If you are using naked spans, it may setup signaling and 
respond to A/B signalling events correctly, but I never had anything to test 
it with as yet.

David

Mark Lipscombe wrote:

> Hi,
> 
> I have finally got my hands on two Dialogic E1 span cards on loan from Intel, 
> I've got the Dialogic drivers working, tested the configuration, compiled and 
> installed Bayonne, and can sucessfully start bayonne and have it (apparently) 
> find all the channels on the two cards.  
> 
> I now have a few of questions if someone feels nice enough to help :)  feel 
> free to tell me to rtfm if i've missed something in the manual
> 
> I've written a few scripts, read the manual, and got a general feel for the 
> scripting language, and a few other bits of information, but for the life of 
> me cant work out how to actually have bayonne run the scripts... how do i do 
> this?
> 
> I need to choose a script to handle the call based on the DNIS information 
> received on the ISDN service, how do I do this with Bayonne?
> 
> Messing with the play command, I noticed that (some) sound files are called 
> like "*::playrec0", what does the "*::" prefix signify?
> 
> And finally, I'm trying to test the configuration without a real primary rate 
> isdn service installed, so I've got a PRI crossover cable, and one card in 
> the bayonne machine, and one in a windows box, and can sucessfully place 
> calls between them using the isdiag utility provided with the dialogic 
> drivers, is it possible to actually make a voice call between them?
> 
> Thanks in advance,
> Mark
> 
> _______________________________________________
> Bayonne-devel mailing list
> Bayonne-devel@...
> http://lists.sourceforge.net/lists/listinfo/bayonne-devel

Ah, never mind. I downgraded to libxml2-2.3.14 (from 2.4) and that seems to have done
the trick.

mseldin wrote:

> I'd appreciate it if anyone could shed some light on my difficulty. When
> I try to test bayonne the following error results:
>
> [root@... server]# ./bayonne --test -dphonedev
> SERVER VERSION 0.6.4; i686 Linux 2.2.14-5.0
> TGI VERSION 2.2; driver=phonedev;
> prefix=/home/bayonne/apps/tgi:/usr/local/libexec/tgi:/bin:/usr/bin:/sbin:/usr/sbin
>
> Loading TGI plugins...
> tgi: initialized; uid=504 pid=31753
> Loading DSO plugin images...
> debug: test module loaded
> Generic Phone Device (phonedev) driver loaded; capacity=16
> dso: loaded 3 functions
> TTS: loading english phrasebooks...
> /home/originals/bayonne/bayonne-0.6.4/modules/xml/bayonne.xml: undefined
> symbol: Parse__9XMLStreamPCc
> network: stopping
> scheduler: stopped
> exiting: reason=-1
>
> I get that following error two separate machines - a redhat 6.2 box and
> a 7.1 box - I've installed libxml2 and recompiled the entire
> distribution from scratch. I've also tried rpms, and the older bayonne
> 0.6.3 release, and I still get the same error. Obviously I'm doing
> something wrong, but I'm confused as to what. During the configuration
> of Common C++ it says it detects the libxml2 libraries successfully.
> I've also tried setting the LD_LIBRARY_PATH to the appropriate
> directories during both compilation and runtime.
>
> Clearly I'm making some error, but I've exhausted every avenue I can
> think of. One final thing which may or may not be connected. While
> CommonC++ does compile and install, the bayonne configure script returns
> this error:
>
> checking for CommonC++ version >= 1.4.0... ./configure: test: ==: binary
> operator expected
> yes
>
> --
>
> __________________________
> Marc Seldin
> Senior Software Engineer
> ShareMedia, inc.
> (240) 631-6131
>
> My cat can eat a whole watermelon.
>
> _______________________________________________
> Bayonne-devel mailing list
> Bayonne-devel@...
> http://lists.sourceforge.net/lists/listinfo/bayonne-devel

--

__________________________
Marc Seldin
Senior Software Engineer
ShareMedia, inc.
(240) 631-6131

My cat can eat a whole watermelon.

I got exactly the same problem. I could not solve it, but a workaround 
is to comment out the XML module out of /etc/bayonne.conf

Probably not much help if you need XML module, but Bayonne will work then...

Michal


mseldin wrote:

>I'd appreciate it if anyone could shed some light on my difficulty. When
>I try to test bayonne the following error results:
>
>[root@... server]# ./bayonne --test -dphonedev
>SERVER VERSION 0.6.4; i686 Linux 2.2.14-5.0
>TGI VERSION 2.2; driver=phonedev;
>prefix=/home/bayonne/apps/tgi:/usr/local/libexec/tgi:/bin:/usr/bin:/sbin:/usr/sbin
>
>Loading TGI plugins...
>tgi: initialized; uid=504 pid=31753
>Loading DSO plugin images...
>debug: test module loaded
>Generic Phone Device (phonedev) driver loaded; capacity=16
>dso: loaded 3 functions
>TTS: loading english phrasebooks...
>/home/originals/bayonne/bayonne-0.6.4/modules/xml/bayonne.xml: undefined
>symbol: Parse__9XMLStreamPCc
>network: stopping
>scheduler: stopped
>exiting: reason=-1
>
>
>I get that following error two separate machines - a redhat 6.2 box and
>a 7.1 box - I've installed libxml2 and recompiled the entire
>distribution from scratch. I've also tried rpms, and the older bayonne
>0.6.3 release, and I still get the same error. Obviously I'm doing
>something wrong, but I'm confused as to what. During the configuration
>of Common C++ it says it detects the libxml2 libraries successfully.
>I've also tried setting the LD_LIBRARY_PATH to the appropriate
>directories during both compilation and runtime.
>
>Clearly I'm making some error, but I've exhausted every avenue I can
>think of. One final thing which may or may not be connected. While
>CommonC++ does compile and install, the bayonne configure script returns
>this error:
>
>checking for CommonC++ version >= 1.4.0... ./configure: test: ==: binary
>operator expected
>yes
>
>
>--
>
>__________________________
>Marc Seldin
>Senior Software Engineer
>ShareMedia, inc.
>(240) 631-6131
>
>My cat can eat a whole watermelon.
>
>
>
>
>_______________________________________________
>Bayonne-devel mailing list
>Bayonne-devel@...
>http://lists.sourceforge.net/lists/listinfo/bayonne-devel
>

You need to have libxml2 on the system and then rebuild Common C++ all over 
again.  Then xml parsing will work.  Yes, alternately, one could comment out 
xml plugins...

David

Michal Bukovjan wrote:

> I got exactly the same problem. I could not solve it, but a workaround 
> is to comment out the XML module out of /etc/bayonne.conf
> 
> Probably not much help if you need XML module, but Bayonne will work 
> then...
> 
> Michal
> 
> 
> mseldin wrote:
> 
>> I'd appreciate it if anyone could shed some light on my difficulty. When
>> I try to test bayonne the following error results:
>> 
>> [root@... server]# ./bayonne --test -dphonedev
>> SERVER VERSION 0.6.4; i686 Linux 2.2.14-5.0
>> TGI VERSION 2.2; driver=phonedev;
>> prefix=/home/bayonne/apps/tgi:/usr/local/libexec/tgi:/bin:/usr/bin:/sbin:/usr/sbin 
>> 
>> 
>> Loading TGI plugins...
>> tgi: initialized; uid=504 pid=31753
>> Loading DSO plugin images...
>> debug: test module loaded
>> Generic Phone Device (phonedev) driver loaded; capacity=16
>> dso: loaded 3 functions
>> TTS: loading english phrasebooks...
>> /home/originals/bayonne/bayonne-0.6.4/modules/xml/bayonne.xml: undefined
>> symbol: Parse__9XMLStreamPCc
>> network: stopping
>> scheduler: stopped
>> exiting: reason=-1
>> 
>> 
>> I get that following error two separate machines - a redhat 6.2 box and
>> a 7.1 box - I've installed libxml2 and recompiled the entire
>> distribution from scratch. I've also tried rpms, and the older bayonne
>> 0.6.3 release, and I still get the same error. Obviously I'm doing
>> something wrong, but I'm confused as to what. During the configuration
>> of Common C++ it says it detects the libxml2 libraries successfully.
>> I've also tried setting the LD_LIBRARY_PATH to the appropriate
>> directories during both compilation and runtime.
>> 
>> Clearly I'm making some error, but I've exhausted every avenue I can
>> think of. One final thing which may or may not be connected. While
>> CommonC++ does compile and install, the bayonne configure script returns
>> this error:
>> 
>> checking for CommonC++ version >= 1.4.0... ./configure: test: ==: binary
>> operator expected
>> yes
>> 
>> 
>> -- 
>> 
>> __________________________
>> Marc Seldin
>> Senior Software Engineer
>> ShareMedia, inc.
>> (240) 631-6131
>> 
>> My cat can eat a whole watermelon.
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Bayonne-devel mailing list
>> Bayonne-devel@...
>> http://lists.sourceforge.net/lists/listinfo/bayonne-devel
>> 
> 
> 
> 
> _______________________________________________
> Bayonne-devel mailing list
> Bayonne-devel@...
> http://lists.sourceforge.net/lists/listinfo/bayonne-devel

Hi,
  I've found some Translators, but I'm not still sure if will be possible t=
o do
things from previous e-mail ...

Best regards,
  Robert

--=20
   _
  |-|  __      Robert Vojta <vojta-at-ipex.cz>          -=3D Oo.oO =3D-
  |=3D| [Ll]     IPEX, s.r.o.
  "^" =3D=3D=3D=3D`o

Each language has it's own DSO translator module.  Hence, a Czech language 
rules module can be written for Bayonne with a different interpretation of the 
rule set, or even which offers new language rules.  When new rules are added 
for one language, an equivilent rule must be created in others.

David

Robert Vojta wrote:

> Hi,
>   I've found this in documentation ...
> 
>   msgswaiting = youhave &number &zero &singular &plural
> 
>   youhave.au "you have" 
>   no.au "no" 
>   msgwaiting.au "message waiting" 
>   msgswaiting.au "messages waiting"
> 
>   and in my opinion and our language needs it's not enough ... Example in
> our language ...
> 
>   "Nemate zadnou zpravu"  "You have no message"
>   "Mate 1 zpravu"         "You have 1 message"      "zpravu"
>   "Mate 2 zpravy"         "You have 2 messages"     "zpravy"
>   "Mate 5 zprav"          "You have 5 messages"     "zprav"
> 
>   Another example ...
> 
>   "Jedna zprava"     - "One message"                "zprava"
>   "Mas jednu zpravu" - "You have one message"       "zpravu"
> 
>   ...
> 
>   In english you have "message" and "messages" only, but in another
> languages there are more than your two equivalents. I haven't look in
> source code yet, but how can bayonne deal with this? Is there a possibility
> to attach different modules for different languages for this? I think that
> there will be more problems with another language support.
> 
> Best regards,
>   Robert

So you gonna give us all your cell number... just in case? ;-p

David Sugar wrote:
> 
> I will be away in Philladelphia for this year's International Softswitch
> Consortium annual meeting until Wed. night.  For those that need to reach me,
> I should be reachable on my cell phone.
> 
> David
> 
> _______________________________________________
> Developers mailing list
> Developers@...
> http://dotgnu.org/mailman/listinfo/developers

Perhaps we should ditch these Pika cards as they dropped Linux support.

What other cards would you recommend? Perhaps Voicetronix (they seem to 
have good and GPL drivers)?
What cards is Bayonne primarily developed on? Any experience?

Thanks,

Michal

David Sugar wrote:

> What I normally use is a Mandrake 7.2 system.  If you do an insmod -f, 
> the kernel modules will install.  They don't hook deeply into the 
> kernel and so are not dependent on kernel versions.  Mostly I think 
> they just map io port access and that the rest is all user space.
>
> Michal Bukovjan wrote:
>
>> Were you successful using the Pika MonteCarlo API - binary kernel 
>> modules with other kernel version than they recommend?
>> Which distribution is it stable under?
>>
>> Thanks,
>>
>> Michal
>>
>> David Sugar wrote:
>>
>>> First, I generally use the newer 2.2.x kernels, as the Pika stuff is 
>>> not kernel dependent at all.  I wonder if this may be an issue.  I 
>>> have not observed this behavior myself, but I will be happy to start 
>>> looking into it...
>>>
>>> David
>>>
>>> Michal Bukovjan wrote:
>>>
>>>> Hello all,
>>>>
>>>> I have a problem with Bayonne server (0.6.4). I have the server 
>>>> setup as IVR for three 4-port Pika Inline GT ISA cards.
>>>>
>>>> The server crashes during heavy loads.
>>>> The crashes occur once in 2 - 5 hours, it looks like a thread (main 
>>>> service thread?) just dies and the server is unresponsive, some 
>>>> lines which are active during crash are held , incoming calls are 
>>>> not picked up and there is no way how to tell the server has crashed.
>>>>
>>>> The crashes seem to occur when more people access the server 
>>>> simultaneously (5 - 8)
>>>>
>>>> bayonne_status always reports the same state. I only know that a 
>>>> thread has crashed when stopping bayonne, it writes no process with 
>>>> such a PID.
>>>>
>>>> Has anyone seen this behaviour? What could be the cause? What can I 
>>>> do?
>>>>
>>>> I wrote a simple watchdog that just restarts the server after some 
>>>> period of time of inactivity, but that is certainly a suboptimal 
>>>> solution.
>>>>
>>>> More information that could help:
>>>>
>>>> - OS Red Hat 6.2, with downgraded kernel to 2.2.5-12 because of 
>>>> Pika drivers
>>>> - using TGI, Perl scripts to connect to a database (Interbase). I 
>>>> am not using bayonne-dfb.
>>>>
>>>> Thanks for any help,
>>>>
>>>> Michal Bukovjan
>>>>
>>>>
>>>> _______________________________________________
>>>> Bayonne-devel mailing list
>>>> Bayonne-devel@...
>>>> http://lists.sourceforge.net/lists/listinfo/bayonne-devel
>>>
>>>
>>>