[Robustness] H.225 & H.245 state info

[Terry L Anderson]

I have been working on collecting the call state information present in various
H.323 network elements.  The goal is to:
1. see what data is present
2. suggest what data must be re-established if a new element takes over (or an
element recovers but has lost call state data) in order to allow the call to
continue at various specified levels of recovery:
    - call can continue but billing data lost
    - call can continue with full billing data
    - etc.

I have certainly not completed this study, but have collected a fairly complete set
of call state data items and put them into a table indicating which element(s) they
reside in.  The plan is to choose a notation to indicate how vital each element is
for various levels of recovery and which other element has the data that can be used
to restore it in the new element.

I will share this much at this time and perhaps we can begin a discussion about
    - completeness (what I have missed)
    - presentation (is there another format that could make the information more
understandable)

I am attaching it as a word document.

--
------------------------------------------------------------
Terry L Anderson              mailto:tla at lucent.com
Tel:908.582.7013   Fax:908.582.6729
Pager:800.759.8352 pin 1704572   1704572 at skytel.com
Lucent Technologies/ Voice Over IP Access Networks/ Applications Grp
Rm 2B-121, 600 Mountain Av, Murray Hill, NJ 07974
http://its.lucent.com/~tla (Lucent internal) http://www.gti.net/tla

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Elements of Call State2.doc
Type: application/msword
Size: 41984 bytes
Desc: not available
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20000331/aa8c0c0e/attachment-0004.doc>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tla.vcf
Type: text/x-vcard
Size: 548 bytes
Desc: Card for Terry L Anderson
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20000331/aa8c0c0e/attachment-0004.vcf>