Hi Benny,<br><br><div><span class="gmail_quote">29 Mar 2007 12:36:21 +0200, Benny Amorsen <<a href="mailto:benny+usenet@amorsen.dk">benny+usenet@amorsen.dk</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Indeed, this is the limitation of Asterisk which we hit most often. In<br>theory, it isn't a big problem, because you just put<br>Dial(SIP/foo&SIP/bar) in the dial plan. Next: someone with that<br>solution needs to be able to join or leave queues. Ok, a bit of
<br>playing around solves that. Then you discover that it's annoying to<br>have one phone ring while you are talking on the other, so you make<br>call groups to handle that problem. Whoops, you need to recognize<br>outgoing calls too, to get them in the call group as well -- but
<br>transferred calls should not be counted. Hackety-hack, fixed that one<br>as well.<br><br>After a while you end up with 10 lines of dial plan per phone. Not<br>nice. It would be much nicer to deal with if the dial command could be
<br>told to return BUSY when just one of the devices it calls is busy.<br>Even better would be multi-registration, of course.</blockquote><div><br>That's exactly what I meant by "simpler" : maybe, you can work around single-registration but it seems to me that things would be much more natural with multi-registration : it's up to your hardphone to offer convenient and flexible behaviour in multi-registration : return BUSY when it has to, allow per-registration call forwarding or logout, MWI, ...
<br><br>Snom phones support multline registration.<br>If Asterisk could also support it ...<br><br>Cheers<br></div></div><br>