proftech | 2023-06-23 23:40:22 UTC | #1

I've looked high & low for a list of delimiters and haven't found one. Reading between the lines looks like space "  " (but only sometimes?), <>, "". Is there a description when to use one or another?

-------------------------

Pooh | 2023-06-24 01:26:21 UTC | #2

Please give more detail what you mean by "delimiters used in extension.conf"

Where are you thinking these delimiters are used?

Delimiters around what?

Even more helpful - what problem are you encountering which makes you ask this 
question?


Antony.

-------------------------

david551 | 2023-06-24 11:04:06 UTC | #3

Each command does its own parsing.  Whilst many use standard code to do this, there can be lots of exceptions.  As such getting a complete list may be rather labour intensive and version dependent. `“”` are not delimiters, but `"` is.  `<>` are not  or not commonly, used as delimiters.  They are used as metacharacters in command descriptions, but they are not entered.

-------------------------

proftech | 2023-06-24 18:31:14 UTC | #4

I can think of at least two cases specifically;
Is it Set(PJSIP_HEADER(add,P-Preferred-Identity)=sip:+12172238767) or Set(PJSIP_HEADER(add,P-Preferred-Identity)=<sip:+12172238767>)?? Either seems to work. The same is true of Set(CALLERID(num)=14175551212) or Set(CALLERID(num)=<14175551212>).

The other case involves strings. Is it "${avariable}" or just ${avariable} (no quotes). I have read that double quotes should always be used but it apparently _**sometimes**_ works without them.

-------------------------

david551 | 2023-06-24 20:16:31 UTC | #5

[quote="proftech, post:4, topic:97487"]
I can think of at least two cases specifically;
Is it `Set(PJSIP_HEADER(add,P-Preferred-Identity)=sip:+12172238767)` or `Set(PJSIP_HEADER(add,P-Preferred-Identity)=<sip:+12172238767>)`?? Either seems to work. The same is true of `Set(CALLERID(num)=14175551212)` or `Set(CALLERID(num)=<14175551212>)`.

[/quote]

Both identity cases are invalid; SIP URIs must have a domain part.  The angle brackets are SIP delimiters, not Asterisk ones.  Apart from the missing domain name, both match the production in the SIP grammar.

In the caller ID, the delimiters are defined by channel driver not the dialplan interpreter.  I always use it without angle brackets, but angle brackets may well work, although it might be channel driver specific, as there are some, undocumented subtleties in this area.

The caller ID is handled a bit like a SIP URI, but with no scheme and no domain.

I've never worked out when Asterisk strips double quotes, and it may well be command specific.  I doubt that it strips them in either of these case, as it would make constructing valid P-P-I and CALLERID(all) values difficult, but I would test if I needed to, initially erring to not using quotes other than as required by the underlying syntax.

Please markup your postings correctly, using </>, the underlying markup, which you can see by looking at https://community.asterisk.org/raw/97487

-------------------------

system | 2023-07-24 20:16:44 UTC | #6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

-------------------------