[Asterisk-Users] PRI maintenance commands

[John Todd]

>At 05:21 PM 12/1/2003, you wrote:
>
>>With multiple inbound PRIs (and hunting across them) coming to multiple
>>[asterisk] servers it is important to be able to do administration, i.e.
>>control which PRIs in the same hunt group take (and which don't take)
>>calls from telco at any given period of time.
>>
>>Our pre-asterisk platform uses SERVICE commands for this purpose to 
>>put B-channels
>>into 'out-of-service'/'maintenance' or 'in-service' state.
>>
>>What is (would be) the asterisk solution? The current libpri doesn't send any
>>SERVICE commands, just acks the incoming ones.
>>
>
>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.
>
>--Ernest

I agree.

Would the method be to "busy out" a particular channel, as it if it 
was "off-hook"?  I think that is the typical method used to indicate 
"maintenance", but then would we reply with "486 busy here" or "480 
temporarily unavailable" on incoming calls to SIP (as an example). 
Are there other code differences that might be the case for other 
channel types?

(PSTN to SIP code maps: 
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/ftmap.htm 
)

As a side note, there is already a bug open on the opposite problem: 
when the switch upstream from * on a PRI turns certain channels off 
for service, * doesn't notice or respond correctly.

http://bugs.digium.com/bug_view_page.php?bug_id=0000054

JT