Re: [asterisk-users] Backport of DEVICE_STATE to 1.4

2011-05-16 Thread Andrew Thomas
https://issues.asterisk.org/view.php?id=15818

That's where I get it from.

If it contains errors, then why not report it there?

Cheers


-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Olivier
Sent: 13 May 2011 15:25
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Backport of DEVICE_STATE to 1.4


Hi,

Here http://www.voip-info.org/wiki/view/Asterisk+func+device_State you
can find a link to download a backported for Asterisk 1.4 version of
DEVICE_STATE function.
(Elsewhere, you can find reference to another backported function
DEVSTATE which seems to behave the same as DEVICE_STATE).

As I would like to prepare as much as possible, my dialplan to 1.6 and
beyond, I would prefer to use DEVICE_STATE if possible.

Anyway, a quick inside this fucn_devstate.c file shows that some (all ?)
Log or Error messages are still refering to DEVSTATE.

My question is which is the best source to get DEVICE_STATE function for
Asterisk 1.4 ?

Regards


 If you have received this communication in error we would appreciate
you advising us either by telephone or return of e-mail. The contents
of this message, and any attachments, are the property of DataVox,
and are intended for the confidential use of the named recipient only.
If you are not the intended recipient, employee or agent responsible
for delivery of this message to the intended recipient, take note that
any dissemination, distribution or copying of this communication and
its attachments is strictly prohibited, and may be subject to civil or
criminal action for which you may be liable.
Every effort has been made to ensure that this e-mail or any attachments
are free from viruses. While the company has taken every reasonable
precaution to minimise this risk, neither company, nor the sender can
accept liability for any damage which you sustain as a result of viruses.
It is recommended that you should carry out your own virus checks
before opening any attachments. 

Registered in England. No. 27459085.



--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Backport of DEVICE_STATE to 1.4

2011-05-16 Thread Olivier
2011/5/16 Andrew Thomas a...@datavox.co.uk

 https://issues.asterisk.org/view.php?id=15818

 That's where I get it from.

 If it contains errors, then why not report it there?

 Cheers



As this bug is considered fixed, I think you can't add any comment
anymore.
Unfortunately, you can still see lines mentionning DEVSTATE function like :

if (ast_strlen_zero(data)) {
ast_log(LOG_WARNING, DEVSTATE function called with no custom 
device
name!\n);
return -1;
}

I opened issue 19300 for that.
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Backport of DEVICE_STATE to 1.4

2011-05-16 Thread Leif Madsen
On 11-05-16 07:29 AM, Olivier wrote:
 As this bug is considered fixed, I think you can't add any comment
 anymore.
 Unfortunately, you can still see lines mentionning DEVSTATE function like :
 
   if (ast_strlen_zero(data)) {
   ast_log(LOG_WARNING, DEVSTATE function called with no custom 
 device
 name!\n);
   return -1;
   }
 
 I opened issue 19300 for that.

Sorry, but backported code is not supported on the issue tracker. You'll need to
use a version of Asterisk that natively supports the DEVICE_STATE() function and
which has maintenance support status (i.e. Asterisk 1.8).

Thanks,
Leif.

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Backport of DEVICE_STATE to 1.4

2011-05-16 Thread Andrew Thomas
Ah! Forgot about that.

Looks like your on your own Olivier.

Sorry


-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Leif
Madsen
Sent: 16 May 2011 13:12
To: asterisk-users@lists.digium.com
Subject: Re: [asterisk-users] Backport of DEVICE_STATE to 1.4


On 11-05-16 07:29 AM, Olivier wrote:
 As this bug is considered fixed, I think you can't add any comment 
 anymore. Unfortunately, you can still see lines mentionning DEVSTATE 
 function like :
 
   if (ast_strlen_zero(data)) {
   ast_log(LOG_WARNING, DEVSTATE function called with no
custom device 
 name!\n);
   return -1;
   }
 
 I opened issue 19300 for that.

Sorry, but backported code is not supported on the issue tracker. You'll
need to use a version of Asterisk that natively supports the
DEVICE_STATE() function and which has maintenance support status (i.e.
Asterisk 1.8).

Thanks,
Leif.

-- _
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


 If you have received this communication in error we would appreciate
you advising us either by telephone or return of e-mail. The contents
of this message, and any attachments, are the property of DataVox,
and are intended for the confidential use of the named recipient only.
If you are not the intended recipient, employee or agent responsible
for delivery of this message to the intended recipient, take note that
any dissemination, distribution or copying of this communication and
its attachments is strictly prohibited, and may be subject to civil or
criminal action for which you may be liable.
Every effort has been made to ensure that this e-mail or any attachments
are free from viruses. While the company has taken every reasonable
precaution to minimise this risk, neither company, nor the sender can
accept liability for any damage which you sustain as a result of viruses.
It is recommended that you should carry out your own virus checks
before opening any attachments. 

Registered in England. No. 27459085.



--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Backport of DEVICE_STATE to 1.4

2011-05-16 Thread Olivier
2011/5/16 Andrew Thomas a...@datavox.co.uk

 Ah! Forgot about that.

 Looks like your on your own Olivier.


Not yet as I found this one :
http://svncommunity.digium.com/svn/russell/asterisk-1.4/func_devstate-1.4/func_devstate.c

In this one, even logs are up to date (ie references to DEVICE_STATE) but I
don't know if there other differences with other backported functions (from
issue 15818, for instance) are meangingful.

Maybe this link could be added to issue 19300 for further reference.

Now it seems I don't have to change my dialplan (for DEVSTATE/DEVICE_STATE)
when moving from 1.4 to 1.6 or 1.8.

Thanks for helping anyway.



 Sorry


 -Original Message-
 From: asterisk-users-boun...@lists.digium.com
 [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Leif
 Madsen
 Sent: 16 May 2011 13:12
 To: asterisk-users@lists.digium.com
 Subject: Re: [asterisk-users] Backport of DEVICE_STATE to 1.4


 On 11-05-16 07:29 AM, Olivier wrote:
  As this bug is considered fixed, I think you can't add any comment
  anymore. Unfortunately, you can still see lines mentionning DEVSTATE
  function like :
 
if (ast_strlen_zero(data)) {
ast_log(LOG_WARNING, DEVSTATE function called with no
 custom device
  name!\n);
return -1;
}
 
  I opened issue 19300 for that.

 Sorry, but backported code is not supported on the issue tracker. You'll
 need to use a version of Asterisk that natively supports the
 DEVICE_STATE() function and which has maintenance support status (i.e.
 Asterisk 1.8).

 Thanks,
 Leif.

 -- _
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

 asterisk-users mailing list
 To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


  If you have received this communication in error we would appreciate
 you advising us either by telephone or return of e-mail. The contents
 of this message, and any attachments, are the property of DataVox,
 and are intended for the confidential use of the named recipient only.
 If you are not the intended recipient, employee or agent responsible
 for delivery of this message to the intended recipient, take note that
 any dissemination, distribution or copying of this communication and
 its attachments is strictly prohibited, and may be subject to civil or
 criminal action for which you may be liable.
 Every effort has been made to ensure that this e-mail or any attachments
 are free from viruses. While the company has taken every reasonable
 precaution to minimise this risk, neither company, nor the sender can
 accept liability for any damage which you sustain as a result of viruses.
 It is recommended that you should carry out your own virus checks
 before opening any attachments.

 Registered in England. No. 27459085.



 --
 _
 -- Bandwidth and Colocation Provided by http://www.api-digital.com --
 New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

 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 --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

[asterisk-users] Backport of DEVICE_STATE to 1.4

2011-05-13 Thread Olivier
Hi,

Here http://www.voip-info.org/wiki/view/Asterisk+func+device_State you can
find a link to download a backported for Asterisk 1.4 version of
DEVICE_STATE function.
(Elsewhere, you can find reference to another backported function DEVSTATE
which seems to behave the same as DEVICE_STATE).

As I would like to prepare as much as possible, my dialplan to 1.6 and
beyond, I would prefer to use DEVICE_STATE if possible.

Anyway, a quick inside this fucn_devstate.c file shows that some (all ?) Log
or Error messages are still refering to DEVSTATE.

My question is which is the best source to get DEVICE_STATE function for
Asterisk 1.4 ?

Regards
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users