<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Nov 20, 2008, at 9:02 AM, Olivier wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">2008/11/20 Daniel Hazelbaker <span dir="ltr"><<a href="mailto:daniel@highdesertchurch.com">daniel@highdesertchurch.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><span class="Apple-style-span" style="color: rgb(0, 0, 0); ">Any reason you want to use the MAC address? If it is just for easy</span></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> provisioning, I just put a MAC address field in the realtime SIP table<br> and use a php script to take the phone's MAC address and feed it the<br> login information it needs.</blockquote><div> </div><div>provisioning is the first reason.<br>I also thought it could help to separate devices, users and other resources.</div></div></blockquote><div><br></div>What I currently do to separate "devices" (fax machines, modems, etc.) is give them actual names. I.e. I have "northFax" and "southFax" defined (so I would type 'sip show peer northFax'). In my mind, and particularly in my use, anything that a person dial's as an extension is going to have a person on the other end. Other things can have names because end users won't be dialing them as extensions. The fax machines are "tied" to a dedicated phone number so Asterisk dial's it internally.</div><div><blockquote type="cite"><div class="gmail_quote"><div><span class="Apple-style-span" style="color: rgb(0, 0, 0); "></span></div></div></blockquote><br><blockquote type="cite"><div class="gmail_quote"><div><span class="Apple-style-span" style="color: rgb(0, 0, 0); ">as you obviously cannot tie MAC address to a dialing string, this forces you to query a database somewhere for every call ...</span></div><div> <br>I'm not fully convinced of this, anyway, but when I thought about it, I felt frightened about loosing things I'm used to ...</div></div></blockquote><div><br></div>Correct. We setup a macro that uses a MySQL database to handle our extension dialing, we don't dial by MAC address but if you were so inclined, I suppose you could. As far as speed goes, we query the database about 4-6 times for every call. 85 users, 9 telco lines, Dell 2950 server, and we peak at about 0.2% cpu usage. Again for simplicity, having all the "front-scene" stuff match what the end-user is talking about is very nice. There is no reason you couldn't do some naming convention like 'user<Extension#>', 'device<Extension#>', 'other<Extension#>'. That might help in your separation and wouldn't be too hard to figure out.</div><div><br></div><div><blockquote type="cite"><div class="gmail_quote"><div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"></font></font></div></div></blockquote>Daniel</div><div><br></div></body></html>