No subject

> I'm trying to add better support to libpri for maintenance
> protocol SERVice and SERVice ACKnowledgement messages.  The
> code is marked in q931.c as being a 'KLUDGE' and should be
> ripe by now for fixing.
>-
> Things work great on my test machine with a T400 and a loop
> back cable.  B-Channels are able to go in and out of
> service, and the state is stored in chan_zap.c so that
> channels out of service are immediately skipped when
> attempting a call on them (similar to Do Not Disturb.)
>-
> Problem is, I can't get it to work in the real world.  And
> given that this is a non-ITU message type, I'm not sure if
> it's me or the switch that doesn't want to play nice.  As
> best I can tell, these SERVice messages are defined in ANSI
> T1.607 with a list price of $360 -- no 3 freebie downloads
> like the ITU specs.  Thus, I've scoured various other web
> resources to cobble together the implementation.
>-
> If I'm correct in my assumptions so far, these NFAS/CCS
> SERVice messages are required for proper operation of backup
> D-Channels, in addition to maintenance of B-Channels.
> Currently, it appears although * supports the use of a
> backup D-Channel, it is not able to initiate a backup
> procedure -- only follow what the far-end switch does.
>-
> I'm attaching a patch of what I have so far, but what I
> could really, really use from some kind soul is a PRI trace
> of a proper SERV exchange for maintenance on a B-Channel.
> If you want to try the patch, it adds CLI commands:
> "zap service enable|disable|loop channel <chan num>"
> (Very similar to the Cisco IOS Dial Technologies command:
> "isdn service <chan num> state 0|1|2")

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0007963 NFAS primary D-channel always being mak...
====================================================================== 

---------------------------------------------------------------------- 
 (0103219) svnbot (reporter) - 2009-04-14 10:55
 http://bugs.digium.com/view.php?id=3450#c103219 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 188344

_U  branches/1.6.1/

------------------------------------------------------------------------
r188344 | jpeeler | 2009-04-14 10:55:45 -0500 (Tue, 14 Apr 2009) | 38
lines

Blocked revisions 188342 via svnmerge

........
  r188342 | jpeeler | 2009-04-14 10:54:16 -0500 (Tue, 14 Apr 2009) | 33
lines
  
  Add service maintenance message support
  
  This is the companion commit to libpri r732. Service messages are now
supported
  for switch types 4ess/5ess. A new option service_message_support has
been added
  to chan_dahdi.conf and is noted in the sample config file. The service
message
  support is turned off by default. The current implementation relies on
AstDB
  to keep track of channel state, which allows the statuses to be
preserved
  across Asterisk restarts. Below is a description of the storage format.
  
  The state and reason for the service state are in the form
<state>:<reason>,
  where:
  <state> ::= { 'O' }  // 'O' ?\226?\128?\147 Out Of Service
  <reason> ::= { '0' | '1' | '2' | '3' }, where:
  '0' ?\226?\128?\147 No reason (backwards compatibility)
  '1' ?\226?\128?\147 NEAR END
  '2' ?\226?\128?\147 FAR END
  '3' ?\226?\128?\147 both NEAR and FAR END
  
  The new CLI commands to handle channel service state are:
  pri service disable channel <chan>
  pri service enable channel <chan>
  
  Many people contributed to the development of this functionality.
Because I
  entered at the very end I do not know the exact history. Special thanks
to 
  all who moved the bug forward one way or another:
  cmaj, PCadach, markster, mattf, drmac, MikeJ, serge-v, murf,
kanelbullar, Seb7,
  tilghman, lmadsen, and especially dhubbard (he answered lots of my
questions
  and did a large portion of the work)
  
  (closes issue http://bugs.digium.com/view.php?id=3450)
  Reported by: cmaj
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=188344 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-14 10:55 svnbot         Checkin                                      
2009-04-14 10:55 svnbot         Note Added: 0103219                          
======================================================================