• Join/Login
  • Business Software
  • Open Source Software
  • For Vendors
  • Blog
  • About
  • More
    • Articles
    • Create
    • SourceForge Podcast
    • Site Documentation
    • Subscribe to our Newsletter
    • Support Request
SourceForge logo
For Vendors Help Create Join Login
SourceForge logo
Business Software
Open Source Software
SourceForge Podcast
Resources
  • Articles
  • Case Studies
  • Blog
Menu
  • Help
  • Create
  • Join
  • Login
  • Home
  • Browse
  • SvxLink
  • Mailing Lists

Re: [Svxlink-devel] Station Info

Brought to you by: sm0svx
  • Summary
  • Files
  • Reviews
  • Support
  • Mailing Lists
  • Tickets ▾
    • Feature Requests
    • Bugs
  • News
Menu ▾ ▴
  • svxlink-announce
  • svxlink-commits
  • svxlink-devel

Re: [Svxlink-devel] Station Info

Re: [Svxlink-devel] Station Info
From: Norbert S. <nse...@ds...> - 2008-10-05 01:06:06
Tobias,
thanks for the info.
It seems that TCL does not like the Quotation marks " ".
I had a few of them in my message and here it went into NOGO
again. After removing the Quotes it sends off mail again.

Cheers,
Norbert, KJ6ZD

Tobias Blomberg wrote:
> On Sunday 28 September 2008 23:10:14 Norbert Seibert wrote:
>   
>> Hi,
>> I ran across a couple of issues with my setup and am not sure if it is
>> already known. or actually supposed to be that way.
>>
>> I noticed that SVXLINK sends out its Station Info content from the EchoLink
>> Module configuration file only if SVXLINK initiates the connection.
>>
>> If a station connects TO the SVXLINK there is no Information appearing
>> on the connecting stations text window that is found in Echo-Link Win on
>> the right hand side of the user interface.
>> I tried it with two different systems with the same results.
>>
>> ReCAP:
>> SVXLINK initiating the connect, Info shows.
>> Other station connecting, no info shows up other than the call letters.
>>     
>
> The message is being sent for sure. You can see this by running Qtel as a 
> client instead of the Windows EchoLink software. There may be a race 
> somewhere causing the message not to show up in the Windows GUI.
>
> Enter the bug info the bug tracker:
>
> http://sourceforge.net/tracker/?atid=573950&group_id=84813&func=browse
>
>
>   
>> The second thing I ran into:
>> I had SVXLINK setup on an XUBUNTU system because of the lesser overhead
>> and running the Link does not really require Open Office, Compiz, Gimp and
>> other gadgets unnecessary  and actually not wanted.
>> I also setup after a couple of fights with the system, the e-mail
>> notification and it worked just fine.
>> Now, since not every one is computer literate (me included) I added some
>> more instructions that I wanted to send along with the Voice Mail retrieval
>> instruction. An error appeared, telling that there was additional character
>> after closing or something like that and I believe some numbers however not
>> the upcoming LOTTO numbers.
>>
>> Nothing in voice-mail worked anymore, the message wasn't stored although
>> SVXLINK announced it was but I found it in an endless loop. The only way to
>> get out, was to abort, The message was not stored locally nor was Mail sent
>> off.
>>
>> It turns out that there are limitations as to how much text I can send in
>> this notification  e-mail. I did not bother to count the exact number of
>> character but I think that the mail buffer is limited and if you run over
>> that limit although an error shows up, nobody at first has an idea why?
>>
>> The endless loop is not desirable and should actually produce another error
>> message "Voice Mail Error" or something like that and exit the module with
>> 0. I am still learning if there is a way to do that in tlc.
>>
>> It took me some time to figure it out since I didn't even think that there
>> would be limitations to the amount of text messages via e-mail.
>> A check for the max character would probably do the trick too, as is done
>> in the Echo-Link Module (Station Info).
>> In this case the SVXLINK would not start and it would be easier to back
>> trace the screwup.
>>
>> Reducing the amount of character fixed the issue and it is happily sending
>> e-mail again.
>>     
>
> I don't think there is a maximum number of characters. However, the 
> configuration file is just another TCL script so the syntax for TCL strings 
> must be followed. Maybe you had some character in the text that TCL did not 
> like (e.g. [ ] { }). I added about 90 lines of text to the config and still 
> there was no problem to send the mail.
>
> 73's de SM0SVX / Tobias
>
>   
>> Thought I get this off my chest!
>> Norbert, 73
>>     
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Svxlink-devel mailing list
> Svx...@li...
> https://lists.sourceforge.net/lists/listinfo/svxlink-devel
>
>   



View entire thread

SourceForge
  • Create a Project
  • Open Source Software
  • Business Software
  • Top Downloaded Projects
Company
  • About
  • Team
  • SourceForge Headquarters
    1320 Columbia Street Suite 310
    San Diego, CA 92101
    +1 (858) 422-6466
Resources
  • Support
  • Site Documentation
  • Site Status
  • SourceForge Reviews
SourceForge logo
© 2026 Slashdot Media. All Rights Reserved.
Terms Privacy Opt Out Advertise