Asterisk Realtime Don’t Support ‘n’ As Extension’s Next Priority

Home » Asterisk Users » Asterisk Realtime Don’t Support ‘n’ As Extension’s Next Priority
Asterisk Users 11 Comments

Hi Team,

I want to used *’n*’ as priority in asterisk realtime but asterisk don’t support n as next priority….

I am using Asterisk 1.4.41

11 thoughts on - Asterisk Realtime Don’t Support ‘n’ As Extension’s Next Priority

  • It is reasonable ‘n’ is not usable as priority number. How can asterisk know the second priority if all other priority have ‘n’ as priority number?
    In a relational database there is no ‘sequential read’.

    In other words, you need to assign the priority to all entries.

    Leandro Il giorno 03/ago/2012 06:27, “virendra bhati” ha scritto:

  • It means ……. Asterisk don’t make any IVR at realtime. It just fire Mysql/Odbc query and get *app and appdata.*

  • Well, what you are wanting would be mathematically impossible!

    A simple text file is read sequentially, so you can infer priorities from the position of lines within the file.

    A database is truly random-access, and so doesn’t have any such natural ordering. You have to indicate the sequence explicitly within a field in each record, and refer to this with an ORDER BY clause.

  • Leandro

    I have to disagree reasonable designers would have done a better job with this one. But we developers are not always so reasonable. The issue is many developers when pushing to put features in they don’t put on their designers hat and think out side the box first.Heaven knows I have been guilty of this one over the years and had to go back and refactor. It is not so reasonable to think that this limitation has to exist developers have been putting order by fields in db driven systems for years. What of the guy who want’s to use n(target) or 4(target) (I know this may have not been an option when RT was first done now it is) so they can add specialized jumping code. If I had been designing the Realtime (today) I
    would have added a field for the priority and made it a full alpha /
    numeric and added an order by field. As it sits now how do you do n, i, h
    or tags ect…. It kinda sucks and limits the Realtime. Not to bash on the developer who did this I get that we don’t always think out side the box all the time nor was some of this ability available when the RT was written. but know it does so what do we do. Unfortunately I am not a ansi C
    guy or I could probably fix it .

    Thanks

    Bryant Zimmerman (ZK Tech Inc.)

    ————————————–

  • I am kissing every inch of land where each one of the asterisk’s developer is putting his feet. In the last 10 years I have worked thanks to the availability of the asterisk code. Most of my income was possible just thanks to asterisk, so I am pretty biased when trying to evaluate if the asterisk code is good or not. You can understand if I “love” the way asterisk has been coded. Nevertheless things can be better and they can be better thanks to you. Asterisk is open source and Mark is a very kind person when you submit patches, so put your ideas in new code and send to him. If you don’t know how to code, hire some developer and have him to code your view of a better RT code. If it will be accepted by the core developer, all us will be happy. if it will not accepted, you’ll be happy with you own personal branch. I run for a small period of time my personal asterisk tree because the italian telephony system is flawed and clients want services not suitable for the general asterisk audience, so there is nothing to worry to have your personal asterisk code.

    Leandro

    PS
    I think your idea of extension RT can be accomplished with some triggers and replacing the extension table with a view on your own n-enabled extension table

    2012/8/3 Bryant Zimmerman

  • That is the sort of thing that might actually be worth submitting upstream.
    There must be loads of dialplans out there that use “same”, “n” and labels all over the place. The only reason mine don’t, is because I’ve been using Asterisk since before these features were introduced and I got used to the old ways.

  • Some might say that you should never do that. I mean, not in one context anyway, where the line numbers matter.

  • The “structured” way of thinking (that cursed philosophy where you write 100
    lines of code to avoid a goto) says you should have your contexts small enough to not need “n”s.

    From: asterisk-users-bounces@lists.digium.com
    [mailto:asterisk-users-bounces@lists.digium.com]

    AJ,

    You don’t use ‘n’s in your dialplan?, you number it yourself? man, what if you have a 300 line dialplan and then you decide to insert a new line in the middle?

    Some might say that you should never do that. I mean, not in one context anyway, where the line numbers matter.

  • If you ever used BASIC you’d remember the trick is to increment line numbers (priorities) by 10. I presume a dialplan would work fine even if the priorities aren’t sequential, as long as they’re increasing monotonically.

    Could someone confirm?

    Having said that, I use n with abandon.

    Regards,

    — Raj

  • No, numbers have to be in sequence.

    Leandro

    I am typing from my mobile phone… Il giorno 03/ago/2012 20:28, “Raj Mathur (राज माथुर)”
    ha scritto:

  • Using “n” with labels is what most people do. A dialplan isn’t javascript, you don’t need two hundred 3 line functions.

    —–Original Message—