Jump to content

ahennis@voicespring.net

Members
  • Posts

    233
  • Joined

  • Last visited

Posts posted by ahennis@voicespring.net

  1. I have not tried yet. This was a feature that I requested and I was just looking at how to use it. I was specifically looking for the global variables (domain-parm1-3). I saw the variables were added to be used in the custom trunk header documentation on the wiki but I did not see anywhere in the wiki of the PBX GUI where I could populate the variables with values.

    My understanding of the feature was that there would be 3 new fields on the Advanced|General Settings page of the domain where I could populate the variables with values. There was also supposed to be 3 new fields added for each extension where I could populate the variables with values.

    I am looking forward to using this feature and am thankful it was added.

  2. That is what I am looking for.

    I was unaware that the Parameter 1 thru 3 on the registration page were being used for this because the documentation says the following and makes no reference at all to them being accessible for use in custom trunk headers.

    • Parameters 1 through 3: Parameters 1 through 3 allow you to configure fixed values that can be used in conjunction with the "External Voicemail System" setting at the domain level. Without using these parameter settings, using a value of 7$u in the "External Voicemail System" setting tells the PBX to prefix the user name (number) with a "7" before sending it to an external voicemail system. If you prefer to set a fixed value (e.g., 555) for the user name, set one of the parameters to a specific extension (e.g., 555) and link it to the "External Voicemail System" setting by entering 7$1 (if using parameter 1) into the "External Voicemail System" setting. The PBX will then use 7555 for the ANI. These Parameter settings can also be used during the dial plan replacement operation. By default, the PBX uses "\r" in the dial plan replacement to substitute "trunk registrar." Similarly, you can use "\x" to use the value set in Parameter 1, "\y" to use the value set in Parameter 2, and "\z" to use the value set in Parameter 3.

     

  3. I have looked everywhere. Even the documentation. The Parameter 1, Parameter 2 and Parameter 3 fields under the registration tab have been there since at least 5.5.0 therefore I can't see how they would be related to a feature put in in v58.

    Other than being the person who requested the feature I know nothing else about it that what has been presented it this thread. Would it be possible to check with the engineer who added the feature as to how the new feature works?

  4. Version 58.0 has this new feature in the release notes:

    Original Caller-ID. As the PBX routes the call through the system it changes the caller-ID. In certain cases the original caller-ID is needed. For this the PBX now makes a copy of the caller-ID when the call hits the PBX. It can be referenced e.g. in the hunt group for displaying the originally called number.

    We are running v59.0 but I do not see anywhere in the hunt groups where you can configure the hunt group to display the originally called number.

  5. Where are they located to put values in them,? I would expect the dom-param1-3 to be on the General Settings for the domain and ext-param1-3 to be somewhere  on the General tab for each extension. I do not see them anywhere. I am running 59.0 with build date of Oct 7 2017 03:01:21

  6. 1 hour ago, Support said:

    Do you mean the PBX should detect the bank holidays by itself and auto assign them to for e.g. service flags every year right?

    No not automatically. I posted about this before. I have installed many Asterisk based system. Asterisk has function called GotoIfTime. Here is a link

    https://www.voip-info.org/wiki/view/Asterisk+cmd+GotoIfTime

    It works a lot like CRON. I can specify a time condition that the system evaluates and returns true or false based on that is programmed. Here is a great example for Thanksgiving

      *,thu,22-28,nov

    Thanksgiving is always on the 3rd Thursday in November and the 3rd Thursday in November can only ever be on the 22nd or 23rd or 24th or 25th or 26th or 27th or 28th of November. Thanksgiving can't be on any other day of the month then those that I have listed.

    Basically here is what is being evaluated.

    Is it Thursday, November 22nd - No so it is not thanksgiving
    Is it Thursday, November 23rd - Yes so it is thanksgiving
    Is it Thursday, November 24th - No so it is not thanksgiving
    Is it Thursday, November 25th - No so it is not thanksgiving
    Is it Thursday, November 26th - No so it is not thanksgiving
    Is it Thursday, November 27th - No so it is not thanksgiving
    Is it Thursday, November 28th - No so it is not thanksgiving

    Asterisk can do this. Asterisk is open source so the code is there to look at to see how it works and program something similar for Vodia PBX.

     

    2 hours ago, Support said:

    Also, yes description is also being noted down. Makes sense.

    This would be very helpful. I understand how much work this is so and that it will take a long time to change the documentation.

    2 hours ago, Support said:

    You would like to do that from domain and extension level respectively right?

    Yes. Basically being able to have a list of which phones have configs at the system level or the domain level or on the extension level.
     

  7. It is great to see the REST API make so much progress since it was first announced. 

    We are a hosted PBX provider so we have multiple servers each having many, many domains. Being able to query and set data for the servers will make maintenance much easier and faster. A very simple example we can look at all servers and all domains to pull lists for automated service flags that have holidays set and verify with the customers what holiday settings are needed for the up coming year. Since there is no mechanism in a service flag to handle floating holidays like Thanks Giving and Labor day, they need to be changed each year. Now we can produce a list of domains and service flags quickly to review with the customers. This will prevent the problem of service flags being set for the incorrect holiday each year.

    It would be useful to have descriptions of the data returned or being set. For example in the Service Flag REST calls returns data like  mon: "00:00-8:AM 20:30-9:AM" which is clearly the hours for the service flag on Monday. There are also things like param1 and param2. What do these things do?

    It would also be useful to query the config templates for each domain and each phone in the domain if that phone has its' own config template. 

  8. We have v59.0 loaded up for testing. I know we can customize the appearance of the logon page using the CSS files. What is the best way to remove that huge picture and make the logon page simpler and more like the old logon page? 

    I also noticed that the "Forgot your password" link is gone. Will that be added back in at some time? 

  9. What PBX version is required to get the configuration templates for the Snom D745?

    Is there any way to add config templates to the PBX? Having to upgrade to a new version of the PBX to support a new model of phone is a pain.

     

    ==========

     

    We are on 5.5.0 and some of the newer versions. I do not see a template for the D725, does it use the 720/D720 template?

     

    BTW. I could not respond to this post so I had to edit my orginal post.

  10. There are many places in the PBX where you need to supply number for a particular parameter.  For example on Agent Groups you have "After hearing ringback for (s) ... " and " Number of agents added per stage: " These fields have drop down menus to select a value. For example "After hearing ringback for (s) " can be set to 5, 10, 15, 20, 30, 60, 120, 180 or 300. What if I need 45 seconds?  It would be nice if these fields were text boxes that you could enter any reasonable value as opposed to having to select from a limited predefined set of values.

  11. I did some additional debugging.

    If I remove the IF statements from the MenuItems I get a choice to turn DND on and one to turn DND off and they both work.

    <MenuItem>
      <Name>{lng dnd_on}</Name>
      <URL>{ssi link snom/menu.xml &amp;name=dnd&amp;value=true}</URL>
     </MenuItem>

     <MenuItem>
      <Name>{lng dnd_off}</Name>
      <URL>{ssi link snom/menu.xml &amp;name=dnd&amp;value=false}</URL>
     </MenuItem>

    If I keep the original code with th IF statements it does not work and I only get the option to turn DND on. I am guessing that there is something wrong with {ssi load extensions ext dnd agent_login} not populating the variables or the variables are not being set.


    {ssi ifn dnd true}
     <MenuItem>
      <Name>{lng dnd_on}</Name>
      <URL>{ssi link snom/menu.xml &amp;name=dnd&amp;value=true}</URL>
     </MenuItem>
    {ssi fin dnd true}

    {ssi if dnd true}
     <MenuItem>
      <Name>{lng dnd_off}</Name>
      <URL>{ssi link snom/menu.xml &amp;name=dnd&amp;value=false}</URL>
     </MenuItem>
    {ssi fi dnd true}

  12. I just noticed that the first IF statement is ifn so it should work when it is compared to true.

     

    {ssi ifn dnd false}
     <MenuItem>
      <Name>{lng dnd_on}</Name>
      <URL>{ssi link snom/menu.xml &amp;name=dnd&amp;value=true}</URL>
     </MenuItem>
    {ssi fin dnd false}

    {ssi if dnd true}
     <MenuItem>
      <Name>{lng dnd_off}</Name>
      <URL>{ssi link snom/menu.xml &amp;name=dnd&amp;value=false}</URL>
     </MenuItem>
    {ssi fi dnd true}

  13. I made the changes for a single Snom d725 as follows and rebooted the phone. It does not seem to be working. If DND is on or off it only has the option to turn DND on.

    How should it work? If DND is off we should see only see a menu option to "Turn DND on" and if DND is ON we should see a menu option to "Turn DND off"?

    Where will the new menu.xml files for the server, domain and each phone be located on the on the PBX? I searched the entire file system and found no files called menu.xml.

     

    {ssi ifn dnd false}
     <MenuItem>
      <Name>{lng dnd_on}</Name>
      <URL>{ssi link snom/menu.xml &amp;name=dnd&amp;value=true}</URL>
     </MenuItem>
    {ssi fin dnd false}

    {ssi if dnd true}
     <MenuItem>
      <Name>{lng dnd_off}</Name>
      <URL>{ssi link snom/menu.xml &amp;name=dnd&amp;value=false}</URL>
     </MenuItem>
    {ssi fi dnd true}

×
×
  • Create New...