I've been trying to install Asterisk/AllStar on my existing X server. The purpose of this is to create a conference bridge, and eventually link it to an existing IRLP/Echolink conference. In time, I hope to run multiple conferences on the server and provide AllStar support for a few conferences. Anyway, I have one show stopping problem and some queries. The show stopper is ztdummy. When I attempt to load it, it causes a kernel panic. The "known issues" so far discovered date back to 2007. Anyone able to unearth any more on this issue? The queries are to do with how I link to the IRLP/Echolink reflector. chan_echolink would be the obvious choice, but to make this work, I would have to bind the Echolink ports to a single IP, so they don't conflict with Echolink on other IPs on the same system. Is this possible? chan_irlp would probably be more problematic, and again it would need to be bound to a specific IP. It would be nice to have some sort of "raw" Speak Freely, RTP or Echolink support, to allow "off grid" links, like I use with thebridge and thelinkbox. I suspect that would require a new channel driver. 73 de VK3JED / VK3IRL http://vkradio.com
I'll start with the "show stopper" ... Tony Langdon, VK3JED wrote:
I've been trying to install Asterisk/AllStar on my existing X server. The purpose of this is to create a conference bridge, and eventually link it to an existing IRLP/Echolink conference.
In time, I hope to run multiple conferences on the server and provide AllStar support for a few conferences.
Anyway, I have one show stopping problem and some queries.
The show stopper is ztdummy. When I attempt to load it, it causes a kernel panic. The "known issues" so far discovered date back to 2007. Anyone able to unearth any more on this issue?
I currently have a few Asterisk systems running within Xen DomUs ... curious where you got the kernel module from ?? What versions are you running of zaptel and the linux kernel ?? I am running zaptel-1.4.12.1 compiled against a 2.6.20 linux kernel. The kernel panic almost seems like the module might be compiled against a different kernel than the one that is running for the DomU. Are there any clues in the panic ?? Do you still have any control over the system after the panic where you might be able to glean some clues from dmesg ?? In addition, there is one modification I've had to make to the zaptel source in order for it run correctly within a Xen DomU. ztdummy attempts to use the RTC which is incorrect on Xen - I've had to comment out part of zaptel-1.4.12.1/kernel/ztdummy.c to prevent it from making that choice. I'll have to locate that fix/change - you'll recognize the issue when asterisk finally starts up w/ ztdummy and complains about timing. - Jeremy, KD0EAV
The queries are to do with how I link to the IRLP/Echolink reflector. chan_echolink would be the obvious choice, but to make this work, I would have to bind the Echolink ports to a single IP, so they don't conflict with Echolink on other IPs on the same system. Is this possible?
chan_irlp would probably be more problematic, and again it would need to be bound to a specific IP.
It would be nice to have some sort of "raw" Speak Freely, RTP or Echolink support, to allow "off grid" links, like I use with thebridge and thelinkbox. I suspect that would require a new channel driver.
73 de VK3JED / VK3IRL http://vkradio.com
At 10:10 PM 8/18/2010, you wrote:
In addition, there is one modification I've had to make to the zaptel source in order for it run correctly within a Xen DomU. ztdummy attempts to use the RTC which is incorrect on Xen - I've had to comment out part of zaptel-1.4.12.1/kernel/ztdummy.c to prevent it from making that choice. I'll have to locate that fix/change - you'll recognize the issue when asterisk finally starts up w/ ztdummy and complains about timing.
Yep, found that one in Google, ztdummy now loads without causing a panic, and got my configuration downloaded off the AllStar server. :) Now, just have to work out how to link it to the rest of the system permanently. :) 73 de VK3JED / VK3IRL http://vkradio.com
On 8/18/10 7:50 AM, Tony Langdon, VK3JED wrote:
At 10:10 PM 8/18/2010, you wrote:
In addition, there is one modification I've had to make to the zaptel source in order for it run correctly within a Xen DomU. ztdummy attempts to use the RTC which is incorrect on Xen - I've had to comment out part of zaptel-1.4.12.1/kernel/ztdummy.c to prevent it from making that choice. I'll have to locate that fix/change - you'll recognize the issue when asterisk finally starts up w/ ztdummy and complains about timing.
Yep, found that one in Google, ztdummy now loads without causing a panic, and got my configuration downloaded off the AllStar server. :)
Was the RTC causing the panic ?? or was there something else you did ??
Now, just have to work out how to link it to the rest of the system permanently. :)
Let us/me know how this goes... I've spent some time trying to make tbd/tlb work with Asterisk; I've managed to make lots of garbled sounds with chan_rtpDir thus far and that's about it. I have used chan_echolink with pretty good success; but I like some of the features that tbd offers. I've done very little with IRLP - I've only gone as far as receiving an experimental IRLP node number a few days ago - but I haven't picked it up much since then. - Jeremy, KD0EAV
73 de VK3JED / VK3IRL http://vkradio.com
At 11:58 PM 8/18/2010, you wrote:
Was the RTC causing the panic ?? or was there something else you did ??
It was the RTC.
Now, just have to work out how to link it to the rest of the system permanently. :)
Let us/me know how this goes... I've spent some time trying to make tbd/tlb work with Asterisk; I've managed to make lots of garbled sounds with chan_rtpDir thus far and that's about it. I have used chan_echolink with pretty good success; but I like some of the features that tbd offers. I've done very little with IRLP - I've only gone as far as receiving an experimental IRLP node number a few days ago - but I haven't picked it up much since then.
Well, chan_rtpdir offers the ideal solution, but on tbd, there are bugs in chan_rtpdir support, due to the repacking code between IRLP and Echolink (that converts between the different packet sizes). When IRLP and chan_rtpdir are both in use, things break. :( The problems are all on the tbd side of things, but it's not a high priority to get fixed. :( Using chan_echolink would require me to be able to bind the Echolink ports to a specific IP, because most of the IPs on the box have a separate tbd or tlb instance listening on the Echolink ports. running Asterisk as the reflector itself is not feasible, there are several hooks needed to interface the reflector binary to the reflector code, and these are quite different to what IRLP expects.
- Jeremy, KD0EAV
73 de VK3JED / VK3IRL http://vkradio.com
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
73 de VK3JED / VK3IRL http://vkradio.com
participants (2)
-
"Jeremy R. Geeo [KDØEAV]" -
Tony Langdon, VK3JED