Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

George Joseph wrote: Why not... ${PJSIP_CONTACT(sip:alice@10.24.19.55:5060 )} => useful information! Including useragent. *AND ACTIVE CHANNEL IF ANY.* Skip the rest if you only need to know if in use. It has pros and cons. It's easy and useful from a user

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

On Mon, Dec 29, 2014 at 11:08 AM, Matthew Jordan wrote: > > > On Mon, Dec 29, 2014 at 11:20 AM, Joshua Colp wrote: > >> Matthew Jordan wrote: >> >> >> >> >>> If we have to define multiple endpoint definitions, then the usefulness >>> of having multiple contacts bound to an AoR diminishes substa

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

On Mon, Dec 29, 2014 at 12:08 PM, Matthew Jordan wrote: > > > On Mon, Dec 29, 2014 at 11:20 AM, Joshua Colp wrote: > >> Matthew Jordan wrote: >> >> >> >> >>> If we have to define multiple endpoint definitions, then the usefulness >>> of having multiple contacts bound to an AoR diminishes substa

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

On Mon, Dec 29, 2014 at 11:20 AM, Joshua Colp wrote: > Matthew Jordan wrote: > > > > >> If we have to define multiple endpoint definitions, then the usefulness >> of having multiple contacts bound to an AoR diminishes substantially. It >> may be that people are confusing the concept of a device

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

On Mon, Dec 29, 2014 at 11:12 AM, George Joseph wrote: > In basic scenarios, however, we do have a match between the inbound >> Contact header in the INVITE request and what was provided by that device's >> REGISTER request. >> >> It is possible, however, to not require Asterisk to make this d

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

Matthew Jordan wrote: If we have to define multiple endpoint definitions, then the usefulness of having multiple contacts bound to an AoR diminishes substantially. It may be that people are confusing the concept of a device with that of a user profile - but if that's the case, then I'm not su

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

On Mon, Dec 29, 2014 at 10:01 AM, Matthew Jordan wrote: > > > On Mon, Dec 22, 2014 at 1:13 PM, George Joseph < > george.jos...@fairview5.com> wrote: > >> >> >> On Mon, Dec 22, 2014 at 12:01 PM, Matthew Jordan >> wrote: >> >>> On Mon, Dec 22, 2014 at 12:53 PM, Joshua Colp wrote: >>> > Currently

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

On Mon, Dec 22, 2014 at 1:13 PM, George Joseph wrote: > > > On Mon, Dec 22, 2014 at 12:01 PM, Matthew Jordan > wrote: > >> On Mon, Dec 22, 2014 at 12:53 PM, Joshua Colp wrote: >> > Currently within PJSIP there is no mechanism for the dialplan to examine >> > things at an AOR or contact level. T

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

On Mon, Dec 22, 2014 at 12:01 PM, Matthew Jordan wrote: > On Mon, Dec 22, 2014 at 12:53 PM, Joshua Colp wrote: > > Currently within PJSIP there is no mechanism for the dialplan to examine > > things at an AOR or contact level. The depth to which you can venture is > > simply the endpoint. > > >

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

Matthew Jordan wrote: I think this gets 90% of the way towards what people (such as X-Rob, who filed ASTERISK-24341) were looking for. I don't think this quite addresses the use case of "I want to create an outbound INVITE request to all contacts on an AoR that do not currently have an activ

Re: [asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

On Mon, Dec 22, 2014 at 12:53 PM, Joshua Colp wrote: > Currently within PJSIP there is no mechanism for the dialplan to examine > things at an AOR or contact level. The depth to which you can venture is > simply the endpoint. > > In practice this can be annoying if you would like to examine things

[asterisk-dev] PJSIP_AOR and PJSIP_CONTACT Dialplan Functions

Currently within PJSIP there is no mechanism for the dialplan to examine things at an AOR or contact level. The depth to which you can venture is simply the endpoint. In practice this can be annoying if you would like to examine things and change an outgoing INVITE (to add a header for auto an