similar to: No subject

Hi, 1. You can now find several SIP harphones with bicolor BLFs (see Polycom, Cisco, ...). Is there a protocol which best describes how to use this bicolor BLD feature ? 2. I would like to map these BLFs to the following user activities : - user is logged off: no light - user is logged in: green light - phone is ringing: blinking light - user is on call: red light It seems that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I must be missing something here but I can't figure out why I can't get DEVICE_STATE() to give me anything other than "NOT_INUSE". I have two extensions: 6666 and 6668. I used 6668 to make a call to yet another phone, so I know that it's busy. I then use 6666 to call 6668 and in the dialplan have a noop to see what

On Tue, Nov 25, 2014 at 10:21 AM, James Lamanna <jlamanna at gmail.com> wrote: > > On Tue, Nov 25, 2014 at 8:14 AM, Matthew Jordan <mjordan at digium.com> > wrote: > >> On Mon, Nov 24, 2014 at 2:12 PM, James Lamanna <jlamanna at gmail.com> >> wrote: >> > Also, how big does the cache in frame.c grow to? >> > I've recompiled with

You can use a custom device state to do it. [dnd] ;DND Toggle exten => *363,1,Answer() same => n,Set(CURRENT_PRESENCE=${DEVICE_STATE(Custom:DND${CHANNEL(peername)})}) same => n,GotoIf($[${CURRENT_PRESENCE}=NOT_INUSE]?*78,1:*79,1) ;DND On exten => *78,1,NoOP(Turning DND On) same => n,Set(DEVICE_STATE(Custom:DND${CHANNEL(peername)})=BUSY) same =>

I'd recommend using DEVICE_STATE On your extension 101, Check the DEVICE_STATE of peer SIP/101, If it's not 'NOT_INUSE' then dial it, Otherwise dial SIP/102 exten => 101,1,ExecIf($["${DEVICE_STATE(SIP/101)}"="NOT_INUSE"]?Dial(SIP/101,40)) same => n,Dial(SIP/102,40,t) same => n,Hangup() On Wed, Feb 25, 2015 at 2:08 PM, ricky gutierrez

On Tue, Nov 25, 2014 at 8:14 AM, Matthew Jordan <mjordan at digium.com> wrote: > On Mon, Nov 24, 2014 at 2:12 PM, James Lamanna <jlamanna at gmail.com> wrote: > > Also, how big does the cache in frame.c grow to? > > I've recompiled with MALLOC_DEBUG on that server: > > > > asterisk -rx "memory show summary" > > > > .... > >

Hi! Trying to figure out what I am doing wrong... 1 std SIP phone (0317998975) registered to an Asterisk (SVN-trunk-r234256) 1 Cell phone 00733025975 attached through H323. extensions.conf exten => 975,1,Goto(975-${DEVICE_STATE(SIP/0317998975)},1) exten => 975-INUSE,1,VoiceMail(0317998975 at inputinterior.se,bs) exten => 975-INUSE,2,Hangup() exten =>

Hi! Have a weired problem with Avaya 9650 phones: extensions.conf exten => 0317998975,hint,SIP/0317998975 exten => 0317998975,1,Goto(0317998975-${DEVICE_STATE(SIP/0317998975)},1) exten => 0317998975,2,Hangup() exten => 0317998975-INUSE,1,VoiceMail(0317998975 at inputinterior.se,bs) exten => 0317998975-INUSE,2,Hangup() exten => 0317998975-NOANSWER,1,VoiceMail(0317998975 at

Hello Have a setup of asterisk with realtime SIP devices. Trying to organise monitoring of my SIP devices. Once device registered, its state becomes NOT_INUSE (result of DEVICE_STATE(SIP/device) function). Simulating of device breakage - powerdown it. Waiting for a while (minute or two), retrieving DEVICE_STATE(SIP/device) again - no changes! Awaited UNAVAILABLE. doing from CLI: sip qualify peer

Hi all! I am trying to figure out how DEVICE_STATE is working, no luck so far. sip.conf [0317998975] type=friend regexten=0317998975 secret=???? username=0317998975 callerid="Magnus Benngard" mailbox=0317998975 at inputinterior.se host=dynamic canreinvite=yes dtmfmode=rfc2833 nat=yes disallow=all allow=alaw extensions.conf exten => 0317998975,hint,SIP/0317998975 exten =>

I have a system running Asterisk 11.2.1 that has had a couple calls between internal extensions get "stuck open". I didn't catch the verbose log for the first one, since I generally don't verbosely log to file, but the second one shows that the call that got stuck was dialed, but the caller hung up before the called device answered. This server is running a hotdesking

Copying to asterisk-users, as it's of use there too. I copied this code years ago from the net, it may have been modified since... This however is only used by managers, as it allows the manager to log a user in and out. For agent logged in/out status: where 8501 is the queue number and 8512 is the agent's extension, and SIP0001 is the agent's device. in extensions.conf

Hi all, How can I implement a full-featured Call-Waiting behavior on the Asterisk level (e.g. I don't want to relay on end-equipment capabilities)? I found it very strange that such a basic feature is not built-in in Asterisk (and I've googled a lot in search for this). Here is what I need: SomeuserX is calling MyUserA. They are on conversation (assumption: voice is via the Asterisk)

Arch = x86_64 OS = CentOS-6.4 (freepbx) Asterisk = 11.4.0 FreePBX = 2.11.0.2 Snom870 Handsets We are in the process of moving to an Asterisk based PBX. At the moment most things work as we wish. However, I have just notices that when I force a reload using 'amportal a reload' I see this loop start in 'asterisk -rvvvvvvvvvv': > Channel Local/s at tc-maint-000002a4;1

an external program, which at this stage, is not customizable ... I don't know if alternatives (LiMO, Android, ...) would be more open to this customization but for Symbian, not only Nokia SIP client wouldn't let you autoanswer to SIP calls, but any other SIP client complying to Symbian design wouldn't support autoanswer. PS: Please, note that I'm far from being an expert in GSM

If you don't use 'CERTVERIFY 1', then this will at least make sure that nobody can sniff your sessions without a large effort (...) > So, do I misunderstand CERTVERIFY directive ? Or is there a bug ? >> Can you reproduce such behaviour ? >> > > I'm not sure what is going on. Can you try running 'upsmon' with debugging > enabled? The following are

That's the main reason I opened this thread as it surprised me a bit ... > > > Any 2-wire analog leg will be a source of echo. Many, many, many calls > do not have a 2-wire leg. Even in handset audio circuit ? I was thinking that any handset is a potential echo source due to this audio circuit ... Do you agree ? > Think cell/mobile or endpoints with PRI or T-1. > >

such file or directory" on pure-IP platform in which I installed asterisk-libpri-dahdi trilogy. Maybe, it's me while following README instructions, maybe README instructions could be improved or maybe it's wrongly labeled messages ? That's why I told myself : I'm waiting too much from doc ? is a pure-IP platform too specific ? what is the official policy ? README starts with

... Thanks, anyway for telling as at least, it reflects your needs. > > > You want NT PtMP and i second that, > not being limited on the asterisk > side is a must in the > telephony ecosystem, since the legacy PABX aren't alwsys easy to > reconfigure. > > _______________________________________________ > -- Bandwidth and Colocation Provided by

connecting legacy PBX to Asterisk (for the very same reason, those PBX use TE-PTMP). If others could join this thread and say if they agree or not with NT-PTMP being the 2nd most needed mode, would be great. Please, do not hesitate to comment. > > > Right now, I would not preclude the possibility that NT-PTMP support > might be added, but I could not give you a concrete time at which