Jump to content

Tom Wellige

Root Moderator
  • Content Count

    2,753
  • Joined

  • Last visited

  • Days Won

    91

Tom Wellige last won the day on September 19

Tom Wellige had the most liked content!

Community Reputation

51 Excellent

3 Followers

About Tom Wellige

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Interests
    SwyxWare, Software Development, Flight Simulation

Recent Profile Visitors

7,129 profile views
  1. Tom Wellige

    EN: Swyx Topia

    This article is taken from the Swyx Forum Archive (2007-2014) and was originally posted 12.07.2009 by Tom Wellige. Swyx Topia is a place in the distant future where... it is believed that there is one client for all platforms, with a fully resize-able/responsive UI/skin the admin msc is a tale which the youngsters refuse to believe that it ever existed the GSE is a web based, cross platform application, easily expandable with new function blocks by every user the concept of the ease of use and administration is the driving factor in all development the Swyx software integrates by default in all other standard software ...
  2. This article is taken from the Swyx Forum Archive (2007-2014) and was originally posted 27.05.2008 by Tom Wellige. The Swyxus Forumus was discussed in a blog article I wrote about a Swyx-Tours trip for a "SwyxECR for Developers" training at the premises of MTV in Surrey, London. I will not quote the entire blog article, but just the relevant part:
  3. This article is taken from the Swyx Forum Archive (2007-2014) and was originally posted 26.11.2008 by wbruessler . Skin, the (feminine). In English, it is easy: "The" skin. But in German it is quite complicated. Sometimes I read "der Skin wird nicht geladen", "das Skin hat zu wenige Namenstasten". Argh! As the inventor, I now declare: SwyxIt! skins are feminine. So please call it "die Skin". Example: "Die Skin von dem Herbert seine Sekretärin ihr SwyxIt!". The only allowed exception for certain regions: "Dat Skin"
  4. Tom Wellige

    EN: Swyxville

    This article is taken from the Swyx Forum Archive (2007-2014) and was originally posted 12.10.2008 by Morten Rokosz. Swyxville is the most organized town in Techland, one quite nice place in Cyberspace. The town is controlled by a governing body called the ECR (Extended Cyber Republic). They are able to solve all problems using the GSE (Goverment Solving Engine). This machine is guarded by an elite of über-nerds using only the native language of VBScript. A language almost forgotten by all others in Techland.
  5. Tom Wellige

    EN: Swyxism

    This article is taken from the Swyx Forum Archive (2007-2014) and was originally posted 03.08.2007 by Morten Rokosz. The belief that SwyxWare is the superior system. That all other systems are just a shadow of the pure code. The faith is based on a document known as 'SwyxWare.pdf'. The true believers of Swyxism are convinced that one day they will see the true path of coding and after this revelation there will never be any bugs in software anymore. Others believe that the system is just a better way to make phonecalls...
  6. This article is taken from the Swyx Forum Archive (2007-2014) and was originally posted 24.07.2007 by Tom Wellige Do not ask what your community can do for you, but what you can do for your community.
  7. This article is taken from the Swyx Forum Archive (2007-2014) and was originally posted 05.06.2007 by Ryan Osborne. A Swyx-o-Holic is a person who Lives, Breaths and Sleeps around Swyx. Examples of a Swyx-o-Holic include; Someone who is addicted with the telephony system Swyx Someone who spends a lot of time configuring Swyx People such as Morten Rokosz and Ryan Osborne who are self confessed Swyx-o-Holics
  8. Natürlich kann die SwyxWare das, halt über das Call Routing. Und da kannst du Dir dann überlegen, wie Du es dem Kunden ermöglichen willst. Ein zentrale Backliste, oder eine Blackliste pro Benutzer. Ein Blacklist Verwaltung über den Call Routing Manager oder eine externe Quelle (z.B. Textdatei, Excel Tabelle oder Datenbank). Du hast da alle Möglichkeiten offen, und das sind ein vielfaches mehr als "... heute zu Tage jede Telefonanlage, von der Fritzbox angefangen ...". Einen möglichen Ansatz findest Du hier im Forum unter: Number Blocking
  9. In former years we had Blogs on the Swyx Forum page and a hand full of regular bloggers, writing more or less about Swyx related topics. One of these old blogs is currently re-posted every Friday: Mirjams' Fridays' Swyx Tip. I wonder if there are users around here, beside me, who would be interested in writing a regular blog? Blogs can of course be written in either German or English language. The frequency of blog posts is totally up to the blogger. To get an idea if it would make sense to setup blogs again, I will start a small poll (on top of this post) and will let it run it for a week or so. If you have further questions about blogs and their possible content feel free to ask in this topic.
  10. Hallo, in meinen Augen ist das nichts fürs Call Routing, da das ja nur durch kommende Rufe auf einen Benutzer getriggert wird. Wenn kein Ruf für einen Benutzer rein kommt, bekommst Du dann auch den Statustext nicht aktualisiert. Denkbar wäre eine kleine Applikation auf den Clients parallel zum SwyxIt!, welche über das Client SDK den Statustext passend setzt, oder eine zentrale Applikation irgendwo (z.B. auf dem Server selbst) welche regelmässig (z.B. alle 10 Minuten) per Config Datastore SDK oder PowerShell alle benötigten Daten ermittelt und setzt. Persönlich würde ich den zweiten Ansatz verfolgen. Das könnte dann in etwa so aussehen: - über das globale Telefonbuch alle Benutzer inkl. aktuellem Status ermitteln - über die Login Device Liste pro Benutzer die IP Adresse des SwyxIt! Clients ermitteln (wobei natürlich auch eine Telefon IP Adresse verwendet werden könnte) - Statustext pro Benutzer passend setzen oder auch löschen (bei abgemeldeten Benutzern)
  11. The old Swyx Forum (2007-2014) had a Wiki open to all users to add tips&tricks and any other kind of information to the forum page. After changing to the current forum system in 2014 the Wiki was only available read-only in the archive. As the archive is disabled now and also on request of some users I have setup a new wiki: SwyxPEDIA Wiki There was (and still is) a SwyxPEDIA area in the forum itself. I just used that to keep content of the old Wiki in the new forum. But the different areas were (and still are) forums and not Wiki articles. Everybody could add to them, but only as posts into a discussion thread. A Wiki is different. In there you have articles and no discussion threads. Everybody is able to work on articles directly. A Wiki keeps the history of all changes, so they can always be reverted (by a moderator). Please feel free to use the Wiki (read, add, edit)!
  12. A huge list of all Extended Call Routing (ECR) related information can be found here: ECR Useful Link Collection
  13. The following is a collection of useful links when it comes to developing add-ons/connectors/extensions for the SwyxIt! The grayed out links in this list a current not available but will be made available again soon. Interfaces SwyxIt! Client SDK SwyxIt! Variables SwyxIt! TAPI Interface (TSP) How-to articles How to open an URL from SwyxIt! How to open an URL from SwyxIt! (on transferred calls) How to obtain line details of an incoming or transferred call How to execute any command on incoming call How to initiate alarm calls programatically How to auto accept incoming calls Event signalling from client line manager into VB script VBScript updates text file with caller information (example for event handling)
  14. This article is taken from the Swyx Forum Archive (2007-2014) and was originally posted 03.07.2014 by me The SwyxIt! Web Extension control and Shortcut buttons supports a set of variables to retrieve certain call related values. Variables names are case insensitive. For the web extension variables can be part of the URL or HTML content. Supported Variables %SelLinePeernumber% is the phone number of the other party (for inbound and outbound calls) on the selected line. %RelatedLinePeernumber% is the phone number of the other party (for inbound and outbound calls) on the line that is linked to the Web Extension. %SelLinePeernumberPublicFormat% is the phone number of the other party (for inbound and outbound calls) in non-canonical format without public access prefix on the selected line (the settings from the user’s location will be used). Example: public access prefix: 0 long distance prefix: 0 international prefix: 00 area code: 231 country code: 49 length of own internal number: 3 digits (eg. 222) The length of internal numbers is guessed from the length of the own internal number. SelLinePeernumber SelLinePeernumberPublicFormat 0003320123456 003320123456 0004940123456 040123456 00049231123456 0231123456 0040123456 040123456 00231123456 0231123456 0123456 0231123456 200 200 %RelatedLinePeernumberPublicFormat% is similar to %SelLinePeernumberPublicFormat% but retrieves the value from the line that is linked to the Web Extension. %SelLinePeername% is the display name of the other party (for inbound and outbound calls) on the selected line. %RelatedLinePeername% is similar to %SelLinePeername% but retrieves the value from the line that is linked to the Web Extension. %SelLinePeeraddress% contains the - %SelLinePeername% and the %SelLinePeernumber% when both details are known - %SelLinePeername% when only the name is known - %SelLinePeernumber% when only the number is known %RelatedLinePeeraddress% is similar to %SelLinePeeraddress% but retrieves the value from the line that is linked to the Web Extension. %SelLineCallednumber% is the own called extension or group extension for inbound calls. This parameter is empty for outbound calls. %RelatedLineCallednumber% is similar to %SelLineCallednumber% but retrieves the value from the line that is linked to the Web Extension. %SelLineCalledname% is the own called name or group name for inbound calls. This parameter is empty for outbound calls. %RelatedLineCalledname% is similar to %SelLineCalledname% but retrieves the value from the line that is linked to the Web Extension. %SelLineCalledaddress% contains the - %SelLineCalledname% and the %SelLineCallednumber% when both details are known - %SelLineCalledname% when only the name is known - %SelLineCallednumber% when only the number is known %RelatedLineCalledaddress% is similar to %SelLineCalledaddress% but retrieves the value from the line that is linked to the Web Extension. %SelLineCallID% is the call id (CDR id) of the current / previous call on the selected line. %RelatedLineCallID% is the call id (CDR id) of the current / previous call on the line that is linked to the Web Extension. %SelLineDisconnectReason% is the disconnect reason of the current / previous call on the selected line. Possible disconnect reasons are: 0 normal disconnect 1 peer was busy 2 peer rejected call 3 call was cancelled 4 call was transferred 6 peer did not pick up, timeout 7 call was already picked up from other phone 9 invalid number was dialed 10 destination is unreachable 12 call routing failed, possible script error (script of peer) 13 permission for call was denied due to call restrictions (e.g. no long distance call allowed) 14 no line available (within ISDN network) 15 no gateway channel available 16 the number of the called party has changed 17 the device type of the called party is incompatible 18 wrong phone number format, e.g. bad character %RelatedLineDisconnectReason% is the disconnect reason of the current / previous call on the line that is linked to the Web Extension. %OwnName% is the own SwyxWare name as displayed in the SwyxIt! display %ActiveServerName% is the name of the active SwyxServer as displayed in the SwyxIt! display Windows environment variables like %PATH% or %APPDIR% are supported as well.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and have taken note of our Privacy Policy.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.