Re: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread Julian Lyndon-Smith
Nope, that is only useful when making a call from the device, not to the device. When I want to call the device, I may want to check / run / process something first that requires a value based on the extension (but is not related in any way) (i.e. extension 706 may be [EMAIL PROTECTED]) Juli

Re: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread C F
you can use set-var in sip.conf to accomplish this same thing. On 6/1/06, Julian Lyndon-Smith <[EMAIL PROTECTED]> wrote: Yeah, I know. Just was hoping to have things the easy way for me. I also want not to have a custom patched box as I know *one* day I'll screw up and lose / forget the patch an

Re: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread Julian Lyndon-Smith
Yeah, I know. Just was hoping to have things the easy way for me. I also want not to have a custom patched box as I know *one* day I'll screw up and lose / forget the patch and wonder why things aint working. Thanks anyway. I'll stop bitching now. Julian. Kevin P. Fleming wrote: Julian Lyndo

Re: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread Kevin P. Fleming
Julian Lyndon-Smith wrote: > Instead now I've got to make sure that the administrator is reminded to > manually update the astdb everytime an email address for the extension > changes or new phones / people are added or removed. As the notes in that original bug told you, there's lots of other wa

Re: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread Julian Lyndon-Smith
That's a shame, as I was hoping to use it. Our sip.conf file is produced automatically by a generator and ftp'd to the * server, so there is no manual editing by the administrator . I was wanting to link an [extension] to an email address so that I can do some stuff in the dialplan. This would

Re: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread Kevin P. Fleming
Julian Lyndon-Smith wrote: > However, the option *did* make it's way into sip.conf, so I guess that > the real bug is that the option is in sip.conf. Yes, and I will fix that in a few minutes. > Devels: Any chance of getting 3359 re-opened and put into asterisk ? No, because it's doesn't really

RE: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread Watkins, Bradley
D] On Behalf Of Julian Lyndon-Smith Sent: Thursday, June 01, 2006 8:31 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] astdb entry in sip.conf Yeah, just found http://bugs.digium.com/view.php?id=3359 where it seems to have been closed out, the code

Re: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread Julian Lyndon-Smith
Sent: Thursday, June 01, 2006 5:02 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] astdb entry in sip.conf Err, I'm not trying to write to the db using the dialplan. In sip.conf there seems to be the ability to automatically create a db entry on

RE: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread Watkins, Bradley
e same result both with the 1.2.8 tarball and svn trunk from this morning. I would file a bug, I guess. - Brad -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Julian Lyndon-Smith Sent: Thursday, June 01, 2006 5:02 AM To: Asterisk Users Mailing List - Non-Com

Re: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread Julian Lyndon-Smith
Err, I'm not trying to write to the db using the dialplan. In sip.conf there seems to be the ability to automatically create a db entry on startup. The line in sip.conf is astdb=chan2ext/SIP/grandstream1=1234; ensures an astDB entry exists But it doesn't ensure an astDB entry exists :) Ju

RE: [Asterisk-Users] astdb entry in sip.conf

2006-06-01 Thread turby
use DBput a DBget (http://www.voip-info.org/wiki/view/Asterisk+database) astdb=chan2ext/SIP/grandstream1=1234 is only variable turby -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Julian Lyndon-Smith Sent: Thursday, June 01, 2006 9:39 AM To: asterisk-