[asterisk-users] The quest for making "hint" more flexible continues - using Realtime now
Ok, now that I've learned I cannot use any variables when using the `hint`
priority (for BLF), I figured I'd try to use the next best thing: hardcoded
values using realtime. This way I avoid variables such as ${ACCOUNTCODE}
but I can at least change the DB more easily than text files. This is the
appropriate line in the DB:
+--+--+---+--++-+
| id | context | exten | priority | app| appdata |
+--+--+---+--++-+
| 2000 | hint-context | 705 | hint | SIP/test-1 | |
+--+--+---+--++-+
This is what I put in mt hint-context in extensions.conf:
[hint-context]
switch => Realtime/[EMAIL PROTECTED]
And this is what I get from the CLI:
Aug 9 11:34:14 NOTICE[19894]: chan_sip.c:11187 handle_request_subscribe:
Got SUBSCRIBE for extension [EMAIL PROTECTED] from xx.xxx.xx.xx, but there is
no hint for that extension
Wellthere is! Is there any way I can do this?
Mike
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] The quest for making "hint" more flexible continues - using Realtime now
Mike wrote:
> Ok, now that I've learned I cannot use any variables when using the
> `hint` priority (for BLF), I figured I'd try to use the next best
> thing: hardcoded values using realtime. This way I avoid variables
> such as ${ACCOUNTCODE} but I can at least change the DB more easily
> than text files. This is the appropriate line in the DB:
>
>
> +--+--+---+--++-+
> | id | context | exten | priority | app| appdata |
> +--+--+---+--++-+
> | 2000 | hint-context | 705 | hint | SIP/test-1 | |
> +--+--+---+--++-+
>
>
> This is what I put in mt hint-context in extensions.conf:
> [hint-context]
> switch => Realtime/[EMAIL PROTECTED]
>
>
> And this is what I get from the CLI:
> Aug 9 11:34:14 NOTICE[19894]: chan_sip.c:11187
> handle_request_subscribe: Got SUBSCRIBE for extension [EMAIL PROTECTED]
> from xx.xxx.xx.xx, but there is no hint for
> that extension
>
> Wellthere is! Is there any way I can do this?
>
> Mike
>
>
> ___
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>http://lists.digium.com/mailman/listinfo/asterisk-users
I personally opened a bug in the bugtracker about this and it was closed
as wont fix. You simply cannot use the hint priority in realtime with
out a major change to the API. So until the code is changed, you are
going to have to have a separate hint context with nothing but hint
priority extensions and set the subscribe context in sip.conf for all
concerned devices to that context.
This is how I am running in production now.
Anthony
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] The quest for making "hint" more flexible continues - using Realtime now
I feared so, but I have already started working on this. Thanks for the
confirmation.
Too bad, the rest of my design was relatively elegant (IMO) and easily to
modify.
Mike
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anthony
Francis
Sent: Thursday, August 09, 2007 12:15
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] The quest for making "hint" more flexible
continues - using Realtime now
Mike wrote:
> Ok, now that I've learned I cannot use any variables when using the
> `hint` priority (for BLF), I figured I'd try to use the next best
> thing: hardcoded values using realtime. This way I avoid variables
> such as ${ACCOUNTCODE} but I can at least change the DB more easily
> than text files. This is the appropriate line in the DB:
>
>
> +--+--+---+--++-+
> | id | context | exten | priority | app| appdata |
> +--+--+---+--++-+
> | 2000 | hint-context | 705 | hint | SIP/test-1 | |
> +--+--+---+--++-+
>
>
> This is what I put in mt hint-context in extensions.conf:
> [hint-context]
> switch => Realtime/[EMAIL PROTECTED]
> <mailto:Realtime/[EMAIL PROTECTED]>
>
> And this is what I get from the CLI:
> Aug 9 11:34:14 NOTICE[19894]: chan_sip.c:11187
> handle_request_subscribe: Got SUBSCRIBE for extension [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]> from xx.xxx.xx.xx, but there is no hint for
> that extension
>
> Wellthere is! Is there any way I can do this?
>
> Mike
> --
> --
>
> ___
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>http://lists.digium.com/mailman/listinfo/asterisk-users
I personally opened a bug in the bugtracker about this and it was closed as
wont fix. You simply cannot use the hint priority in realtime with out a
major change to the API. So until the code is changed, you are going to have
to have a separate hint context with nothing but hint priority extensions
and set the subscribe context in sip.conf for all concerned devices to that
context.
This is how I am running in production now.
Anthony
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] The quest for making "hint" more flexible continues - using Realtime now
is subscribe context an addiotional switch/field ?
or its the peer context ?
On 8/9/07, Mike <[EMAIL PROTECTED]> wrote:
>
> I feared so, but I have already started working on this. Thanks for the
> confirmation.
>
> Too bad, the rest of my design was relatively elegant (IMO) and easily to
> modify.
>
>
>
> Mike
>
>
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Anthony
> Francis
> Sent: Thursday, August 09, 2007 12:15
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [asterisk-users] The quest for making "hint" more flexible
> continues - using Realtime now
>
> Mike wrote:
> > Ok, now that I've learned I cannot use any variables when using the
> > `hint` priority (for BLF), I figured I'd try to use the next best
> > thing: hardcoded values using realtime. This way I avoid variables
> > such as ${ACCOUNTCODE} but I can at least change the DB more easily
> > than text files. This is the appropriate line in the DB:
> >
> >
> >
> +--+--+---+--++-+
> > | id | context | exten | priority | app| appdata
> |
> >
> +--+--+---+--++-+
> > | 2000 | hint-context | 705 | hint | SIP/test-1 |
> |
> >
> +--+--+---+--++-+
> >
> >
> > This is what I put in mt hint-context in extensions.conf:
> > [hint-context]
> > switch => Realtime/[EMAIL PROTECTED]
> > <mailto:Realtime/[EMAIL PROTECTED]>
> >
> > And this is what I get from the CLI:
> > Aug 9 11:34:14 NOTICE[19894]: chan_sip.c:11187
> > handle_request_subscribe: Got SUBSCRIBE for extension [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]> from xx.xxx.xx.xx, but there is no hint for
> > that extension
> >
> > Wellthere is! Is there any way I can do this?
> >
> > Mike
> > --
> > --
> >
> > ___
> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
> >
> > asterisk-users mailing list
> > To UNSUBSCRIBE or update options visit:
> >http://lists.digium.com/mailman/listinfo/asterisk-users
> I personally opened a bug in the bugtracker about this and it was closed
> as
> wont fix. You simply cannot use the hint priority in realtime with out a
> major change to the API. So until the code is changed, you are going to
> have
> to have a separate hint context with nothing but hint priority extensions
> and set the subscribe context in sip.conf for all concerned devices to
> that
> context.
> This is how I am running in production now.
>
> Anthony
>
> ___
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
> ___
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>http://lists.digium.com/mailman/listinfo/asterisk-users
>
--
Mike
Sales Manager
http://www.voicemeup.com
Making it happen
1.877.807.VOIP (8647)
1.514.312.7030
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
