It reports the wrong callsign. The node connecting or disconnectng from echolink is some off the wall callsign that does not correspond with the node number. But it connects fine.

Sent from my iPhone

On Jul 11, 2012, at 3:47 PM, pete M <petem001@hotmail.com> wrote:

What do you mean by incorrect callsing?
 
 
Sent: Wednesday, July 11, 2012 3:41 PM
To: Monty
Subject: Re: [App_rpt-users] echolink stuff
 
Ive used this but the incorrect callsign is being reported. I downloaded latest code from svn but problem still there.
 


Sent from my iPhone

On Jul 11, 2012, at 2:50 PM, Monty <monty@ke7jvx.com> wrote:

It is a setting in /etc/asterisk/rpt.conf:
 
eannmode=3                     ; Default: 1 = Say only node number on echolink connects
                                        ; 2 = say phonetic call sign only on echolink connects
                                        ; 3 = say phonetic call sign and node number on echolink connects
 

Monty


On Wed, Jul 11, 2012 at 11:22 AM, pete M <petem001@hotmail.com> wrote:
Is there a way for a node to specify the call sign rather then the node number whe they connect from echolink? ( I am using the acid distro)
 
If someone connect by the portal we can hear that ve2xx conected, but from the echolink we will hear node 12345 connected..
 
And where can I write information, like on echolink, that describe the repeater and stuff..
 
And finally is there a how to for the echolink part, did not found much..
 
Pierre
VE2PF
 
 
 
 

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

 
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users