[Migrated from old forumParticipant April 5, 2015 at 10:37 am Post count: 327]

in reply to: queue bug(?) #5667 |

I’m not following you. what you say is true as far as what freepbx and elastix puts into the queues_additional.conf file, but i don’t understand how that helps me use queues that support followme and don’t crash asterisk with VDP on a freebpx system.

as i state in my original note, the only way that i can get queues to work on VDP is to put create the queues in freepbx with extensions starting with S (S101, etc). if you don’t put on the S, the system simply crashes in a few hours as it fills up the log. and if you DO use the S you don’t get follow me from asterisk.

so what i would like to know is: what is the recommended way to create and use queues that support followme in VDP? can the queues be created in freepbx or is there some other way you suggest? do you have to put the S on or crash your system? (seems this should be documented if that’s the case)

[Migrated from old forumParticipant April 5, 2015 at 10:35 am Post count: 327]

in reply to: queue bug(?) #5665 |

skyrun,

I don’t think this is VDP bug. Please check queues_additional.conf file in etc/Asterisk folder. This file is generated by Elastix. So, if you type 101 in static agent field Elastix will deploy the following line in queues_additional.conf: member=Local/101@from-queue/n,0 and if you type S101 you will get line: member=SIP/101,0.
That’s way your queue becomes recursive.

Raman

[Migrated from old forumParticipant April 5, 2015 at 10:27 am Post count: 327]

in reply to: New Features #5662 |

Hi,

Ideas for future product improvements we receive are extremely valuable to us.
Our product management team will take it into consideration together with a number of other ideas we received and determine the priorities we will work on in the future.

Please check our web site occasionally for news about Visual Dialplan.

Thank you.

Michael Denich
Apstel support team

[Migrated from old forumParticipant April 5, 2015 at 10:26 am Post count: 327]

in reply to: 1.6 to 1.8 dialplan upgrade #5660 |

I’ve already deployed the 1.6 dialplan and it works.

Waiting for the new version.

Thank you.

Marco Tarini

[Migrated from old forumParticipant April 5, 2015 at 10:26 am Post count: 327]

in reply to: 1.6 to 1.8 dialplan upgrade #5659 |

Hello Tarmak,

It is a bug. The next Visual Dialplan release will have this bug fixed.
In the meantime you may try to deploy the dial plan version 1.6 to Asterisk server version 1.8 since there are no major changes in the dial plan structure between these two versions.
Of course, there are several new functionality introduced in Asterisk 1.8 but the dial plan developed for Asterisk 1.6 should work with Asterisk 1.8, so please feel free to deploy your 1.6 dial plan.

Michael Denich
Apstel support team

[Migrated from old forumParticipant April 5, 2015 at 10:22 am Post count: 327]

in reply to: Skype for Asterisk #5657 |

Hello Stephon,

Yes, Visual Dialplan will support Skype for Asterisk in one of coming releases.

Michael Denich
Apstel support team

[Migrated from old forumParticipant April 5, 2015 at 7:27 am Post count: 327]

in reply to: Can I import existing Asterisk dial plan code #5655 |

Sure it is!
Very powerful and feature rich tool, and I am learning something new every day working with it. The next thing I’ll try is to pool some data from the remote MySQL database using Integration Server. I’ll let you all know how it goes.
top of page

[Migrated from old forumParticipant April 5, 2015 at 7:26 am Post count: 327]

in reply to: Can I import existing Asterisk dial plan code #5654 |

Daniel,
Glad to hear it! I think you’ll find Visual Dialplan as indispensable as I do in creating dialplans. I use it all the time, especially for DB integration with other systems, such as customer information and billing systems. Truly a treat to work with something this powerful.

Kevin

[Migrated from old forumParticipant April 5, 2015 at 7:26 am Post count: 327]

in reply to: Can I import existing Asterisk dial plan code #5653 |

Thanks Michael and Kevin, this is very helpful.
I tried Include and Custom Code and it works (not like my imaginary import but still, this works ;).
I reorganized my hand made code better to Include it in Visual Dialplan while some specific modules are moved to Custom Code.

Thanks!

[Migrated from old forumParticipant April 5, 2015 at 7:26 am Post count: 327]

in reply to: Can I import existing Asterisk dial plan code #5652 |

Hello Daniel,

Although import functionality is not implemented at this moment (as far as I know), there are other functionality that are implemented and that you may find useful to include dial plan developed with Visual Dialplan to your existing extensions.conf dial plan or to move your extensions.conf code to Visual Dialplan.

How to include dial plan developed with Visual Dialplan to existing extensions.conf dial plan?

If you want to include dial plan developed with Visual Dialplan to your existing extensions.conf you will probably benefit from using include statement.
Simply add include statement in your existing extensions.conf to include the file developed with Visual Dialplan.
For example, if you want to name the file developed with Visual Dialplan ‘extensions-apstel.conf’ you will need to:
– rename the output file at preferences dialog (default is extensions.conf for Plain Asterisk server type, but you can rename it to whatever you want, rename it to extensions-apstel.conf)
– deploy extensions-apstel.conf file to your Asterisk server (using Visual Dialplan)
– add include statement into your existing extensions.conf to include newly created extensions-apstel.conf file, and reload the dial plan
That’s it.
When new call arrives the dial plan in extension.conf will be executed and newly created extensions-apstel.conf file will be included and extecuted too.
This way your existing extensions.conf file will not be changed and you’ll work with extensions-apstel.conf file only.

This approach is good if you want to keep existing extensions.conf file and keep working on new part of the dial plan in Visual Dialplan (separate branch or module or separate logical part of the dial plan).

How to move extensions.conf or part of extensions.conf to new dial plan developed with Visual Dialplan?

If you want to do that you will probably benefit the most from Include functionality and Custom Code component.

With Include functionality you can include existing traditional asterisk dial plan code or part of the existing traditional Asterisk dial plan code into Visual Dialplan and keep maintaining that part of the dial plan separately from the Visual Dialplan, in a traditional manner. This functionality can be very useful if you have structurally developed Asterisk dial plan code because you can Include those modules/parts of the code into Visual Dialplan and continue further development in Visual Dialplan leveraging existing modules you already have.

You may also find useful Custom Code Component (available in Visual Dialplan Professional version only) that will allow you to write or reuse already developed traditional asterisk dial plan code and to keep that code inside the Visual Dialplan graphical diagram within the Custom Component.

Michael Denich

Apstel support team

[Migrated from old forumParticipant April 5, 2015 at 7:25 am Post count: 327]

in reply to: Can I import existing Asterisk dial plan code #5651 |

Daniel,
As far as I know you cannot currently import existing dialplan code into VDP and show it graphically. The easiest thing to do is just create a new dialplan in VDP and design it to emulate the functionality of your existing hand code. It should take you less time to design using VDP so you shouldn’t really “lose” any time recreating your existing logic.

Kevin

[Migrated from old forumParticipant April 5, 2015 at 7:07 am Post count: 327]

in reply to: Update problem #5649 |

Hello,

There is known bug in Visual Dialplan v.3.0.04 related to Asterisk DB components.
The new release (v.3.0.05) with the bug fix is available for download.