[asterisk-users] gpx2000 Busy Lamp Field
Cary Fitch
caryf at usawide.net
Wed Mar 25 11:23:01 CDT 2009
Really nothing elaborate to this part: We have the dual entries because some
extensions are/were treated as 3 digit extensions and some as full
NPANXXXXXX. Better safe than sorry.
These Hints are in the Context handling these phone numbers. (They have to
be.)
;Provides LED Lights on phones .
exten => 401,hint,SIP/3983551401
exten => 402,hint,SIP/3983551402
exten => 403,hint,SIP/3983551403
exten => 405,hint,SIP/3983551405
exten => 407,hint,SIP/3983551407
exten => 408,hint,SIP/3983551408
exten => 409,hint,SIP/3983551409
exten => 3983551401,hint,SIP/3983551401
exten => 3983551402,hint,SIP/3983551402
exten => 3983551403,hint,SIP/3983551403
exten => 3983551405,hint,SIP/3983551405
exten => 3983551407,hint,SIP/3983551407
exten => 3983551408,hint,SIP/3983551408
exten => 3983551409,hint,SIP/3983551409
On Snoms the BLF field is 'complex', because it is the hint ID and the
server address, but you don't have to relate the BLF to a line button.
On GXP2000s the BLF field has to be related to a line button that is part of
the context involved, but then the phone id (phone number) is all that is
needed in the data field. If the associated Line button number is changed,
then the BLFs would probably stop working.
Hope this helps. The numbers have been munged to avoid hacker kiddies. :-)
Cary Fitch
_____
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Leonja Cerebro
Sent: Wednesday, March 25, 2009 11:04 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] gpx2000 Busy Lamp Field
Hello Cary,
Can I see your configuration files in any form, I mean only part of BLF
settings
2009/3/25 Cary Fitch <caryf at usawide.net>
We are not having a problem in the BLF area, and we do qualify our remote
phones. I don't know if "qualify" does any thing beyond pinging the
address, but perhaps it does carry a data payload too.
Cary Fitch
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Ken Williams
Sent: Wednesday, March 25, 2009 7:06 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] gpx 2000 Busy Lamp Field
I seem to recall qualify being part of the problem. I'm not qualifying any
extensions. In addition, the BLF I'm doing is for parked lines not for SIP
extensions, so not sure if that's part of the problem either.
I do not recall seeing the notify messages you're asking about, but I
believe that's because of the two things mentioned above.
Ken
-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Vieri
Sent: Wednesday, March 25, 2009 1:41 AM
To: asterisk-users at lists..digium.com
<mailto:asterisk-users at lists.digium.com>
Subject: Re: [asterisk-users] gpx 2000 Busy Lamp Field
Out of shear curiosity, do you mind running "asterisk -rx "show hints" |
grep <your_exten>" 16 minutes after you unplugged your phone, as in my
example test below?
Also, in the * CLI or log, do you see a message such as:
Extension Changed 4063[ext-local] new state XXX for Notify User 4062
right when your phone's registration expires?
or when "asterisk -rx "sip show peers" | grep <your_exten>" gives an UNKNOWN
status (if you use qualify for that SIP extension)?
I'm just wondering where is my Asterisk version (1.4.24) failing compared to
yours.
Thanks,
Vieri
--- On Tue, 3/24/09, Ken Williams <ken at intermountainelectronics.com> wrote:
> I recall having similar issues early
> in Asterisk 1.4...but currently running 1.4.17 and BLF works
> great with a phone expiration of 15 minutes.
>
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com]
> On Behalf Of Vieri
> Sent: Tuesday, March 24, 2009 1:02 PM
> To: asterisk-users at lists.digium.com
> Subject: Re: [asterisk-users] gpx 2000 Busy Lamp Field
>
>
> I'm afraid this isn't a GXP2000 bug but a broken feature in
> Asterisk 1.4, unless I'm overlooking something (it should
> affect any phone with BLF; I only have GXP2000 sets).
>
> I don't have 1.6 yet so I can't see if BLF behaves the same
> way.
>
>
> --- On Tue, 3/24/09, Jon Pounder <jonp at inline.net>
> wrote:
>
> > I see much the same except I think if you investigate
> > further, the light
> > will be green whether the phone ever registered or
> not.
> >
> > > --- On Tue, 3/24/09, Ken Williams <ken at intermountainelectronics.com>
> > wrote:
> > >
> > >
> > >> Our work around is to lower the
> > >> registration expiration on the phones.
> > >>
> > >
> > > Well, something's not working as "I expect it
> to". My
> > GXP2000 phones have re-registration timeout of 2
> minutes.
> > >
> > > In my example below, extension 4061 is unplugged
> (so
> > obviously it won't re-register, ever). Meanwhile, the
> other
> > GXP2000 phones keep seeing 4061 as "on-line" (green
> led).
> > > This happens with Asterisk 1.4.24.
> > >
> > > If I use Asterisk 1.2, the green LED turns red
> within
> > a few seconds.
> > >
> > > My guess is that Asterisk is not sending the
> device
> > state, or it's not correctly detecting that the phone
> has
> > not re-registered.
> > >
> > > I might not be interpreting the "hints" logic
> > correctly, but I suppose that if a "sip show peer"
> reveals
> > that the extension is not registered (when it was
> before)
> > then Asterisk should send out a message to all
> subscribed
> > phones so that their BLF can be updated.
> > >
> > > As you can see below, 4061 is switched off,
> isn't
> > physically online anymore, but all BLF LEDs are
> green.
> > >
> > > Why is this?
> > >
> > > # asterisk -rx "sip show peers" | grep 4061
> > > 4061/4061
> > (Unspecified)
> > D N A 0
> > UNKNOWN
> >
> > > # asterisk -rx "sip show peer 4061"
> > >
> > >
> > > * Name
> > : 4061
> > > Secret
> > : <Set>
> > > MD5Secret : <Not
> > set>
> > > Context :
> > from-internal
> > > Subscr.Cont. : <Not set>
> > > Language :
> > en
> > > AMA flags : Unknown
> > > Transfer mode: open
> > > CallingPres : Presentation
> > Allowed, Not Screened
> > > Callgroup : 2
> > > Pickupgroup : 2
> > > Mailbox :
> > 4061 at device
> > > VM Extension : *97
> > > LastMsgsSent : 0/0
> > > Call limit : 50
> > > Dynamic : Yes
> > > Callerid :
> > "device" <4061>
> > > MaxCallBR : 384 kbps
> > > Expire
> > : -1
> > > Insecure :
> > no
> > > Nat
> > : Always
> > > ACL
> > : Yes
> > > T38 pt UDPTL : No
> > > CanReinvite : No
> > > PromiscRedir : No
> > > User=Phone : No
> > > Video Support: No
> > > Trust RPID : No
> > > Send RPID : No
> > > Subscriptions: Yes
> > > Overlap dial : Yes
> > > DTMFmode :
> > rfc2833
> > > LastMsg : 0
> > > ToHost
> > :
> > > Addr->IP :
> > (Unspecified) Port 0
> > > Defaddr->IP : 0.0.0.0 Port
> > 5060
> > > Reg. exten :
> > > Def. Username: 4061
> > > SIP Options : (none)
> > > Codecs
> > : 0x2 (gsm)
> > > Codec Order : (gsm:20)
> > > Auto-Framing: No
> > > Status
> > : UNKNOWN
> > > Useragent : Grandstream
> > GXP2000 1.1.6.46
> > > Reg. Contact :
> > sip:4061 at 10.215.146.161:5060;transport=udp
> > >
> > > # asterisk -rx "show hints" | grep 4061
> > >
> > 4061 at ext-local
> > : SIP/4061&Custom:DND4
> > State:Idle
> > Watchers 1
> > >
> > *764061 at ext-dnd-hints
> > : Custom:DEVDND4061
> > State:Idle
> > Watchers 0
> > >
> > *214061 at ext-findmefollow :
> > Custom:FOLLOWME4061 State:Idle
> > Watchers 0
> > >
> > >
> > > PS: (I don't understand why 4061 at ext-local has
> > "State:Idle")
> > >
> > > Thanks,
> > >
> > > Vieri
> > >
_______________________________________________
-- 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
_______________________________________________
-- 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
--
We never did too much talking anyway
So don't think twice, it's all right
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090325/e07cb0ba/attachment-0001.htm
More information about the asterisk-users
mailing list