So how do you connect your Allstar node to your Echolink node - when you are
behind a firewall.
For example. my external ip address is 24.xx.xx.xx (a public address to the
internet world). my allstar server which has my echolink node on it, it on
a private address of 192.168.xx.xx. There is a Nat between the 2. When I
try to connect my allstar node on the same server to my echolink node, I get
a connection failed because it tried to connect to the 24.xx.xx.xx address
which it can't see.
I'll go see if my router has the ability to spoof that address as some do.
I can't believe I'm the only one that might have experienced this problem.
Just curious how others have remedied it.
Alan
Sorry, guys, it looked like the mail wasn't being sent, so I clicked on the mouse a few more times...
George J Csahanin
W2DB
Cedar Park, TX
512-401-2630
401-338-0568 cel
Dear Team,
I am trying to get USB Fob but I am not able to make it interact with chan_usb of Asterisk.
My lsbus shows
ID 05e3 : f206 Genesys Logic.
ID 0d8c : 000e C-Media Electronics
Best Regards
Jay Prakash Singh
M:+91-9320049718
Didn't forget about documenting. I wanted to make sure everything is working. It almost was. I found that due to the newer kernels there are some changes that need to be made. Specific to zaptel and USB. Most of those were addressed on app_rpt mail list but I found a couple others. It might be that the easiest thing for me to do will be to create a branch in git for my changes and give you the link to that. I'm not sure why these changes were never driven into the sources.
Specific to the newer kernels the path to the sys dir was changes and the structure of that path makes asterisk not find the USB when they channel driver is loaded.
I think i have that functional now.
I've not looked at the svn, maybe I'll verify against that and create a git branch from it as a starting point. To date my baseline is the files.tar.gz on the stats.allsterlink.org/dl/installcd site
More testing in the next couple of days.
Happy holiday everyone.
Ps. At some pint I'm going to see if I can't make irlp and allsatar coexist on the same box seeing as I have them both running under Debian now,
Alan
Ok, so do the URI's need the snd-usb-audio kernel module? Or is there a
direct interface built into asterisk (kinda doubt the later but figured I'd
ask). My URI's showed up today! :)
I'll be playing *hard* all weekend and it's a long one!
Yeah
Alan
Awesome,
Thanks Matt, Yeah, another notch in the pole… I have Echolink working… And I just go UPS confirmation that my new NXDN repeaters will be here by the weekend… :)…. Yea - don't ask! :)…But it gonna be a fun challenge…
Alan
From: Matt Roberts [mailto:n9gmr@me.com]
Sent: Wednesday, May 23, 2012 10:42 PM
To: Alan Adamson
Subject: Re: [App_rpt-users] Ok, got Echolink working
The W7QO-R node number should be put in the file. If you'd rather use the W7QO node number, you can switch them.
Matt Roberts
n9gmr(a)me.com
Sent from my iPhone
On May 23, 2012, at 10:10 PM, Alan Adamson <adamson_alan(a)hotmail.com> wrote:
So quick question…
My original echolink node was assigned to just my callsign W7QO, my W7QO-R was the issue, it had not been validated… which I just did and everything started to work then … .duh… But it also appears that W7QO-R got a new node number…
So which one goes in the echolink.conf file? The new none that matches W7QO-R? I'm assuming so…
Alan
_______________________________________________
App_rpt-users mailing list
App_rpt-users(a)ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
So quick question.
My original echolink node was assigned to just my callsign W7QO, my W7QO-R
was the issue, it had not been validated. which I just did and everything
started to work then . .duh. But it also appears that W7QO-R got a new node
number.
So which one goes in the echolink.conf file? The new none that matches
W7QO-R? I'm assuming so.
Alan
