<html>
<body>
At 05:21 PM 12/1/2003, you wrote:<br>
<blockquote type=cite class=cite cite><font size=2>With multiple inbound
PRIs (and hunting across them) coming to multiple</font> <br>
<font size=2>[asterisk] servers it is important to be able to do
administration, i.e.</font> <br>
<font size=2>control which PRIs in the same hunt group take (and which
don't take)</font> <br>
<font size=2>calls from telco at any given period of time.</font>
<br><br>
<font size=2>Our pre-asterisk platform uses SERVICE commands for this purpose to put B-channels</font> <br>
<font size=2>into 'out-of-service'/'maintenance' or 'in-service' state.</font> <br><br>
<font size=2>What is (would be) the asterisk solution? The current libpri doesn't send any</font> <br>
<font size=2>SERVICE commands, just acks the incoming ones.</font> </blockquote><br>
Sounds like this could be extended to affect all * channel types. So, the command "channel SIP/ernest quiesce" should have the same logical effect as "channel ZAP/1 quiesce". Write this into the channel drivers and let them take care of sending whatever up/down/quiesce/loopback/etc signals need to be sent. Just a thought.<br><br>
--Ernest</body>
</html>