|
List Info
Thread: H460 features
|
|
| H460 features |
 
United States |
2007-02-15 00:39:08 |
|
To All
For quite sometime I have been working on H.460 framework in OpenH323
(which will eventually be ported (if possible) to Opal). The H.460
framework is a modular script type framework which enables the addition
of new custom features to the stack. H.460 support is included in almost
all RAS and H.225 signalling messages (either GenericData or FeatureSet
field) and can be used to deploy almost any custom function without
having to modify large sections of the stack.
I have checked in 3 example features (in the h323plugins branch) to
demonstrate the power of the H.460 framework
ShortMessaging
This allows H.323 to establish a lightweight call setup for the purpose
of exchanging text based messages. It utilises the
CallIndependentSupplementaryService conference goal to
establish a signalling only connection for the purpose of exchanging
short messages either as a 1 time SMS style or a classic Text Messaging
session. It can also be used to exchange messages during an existing
call. For instance to send a hyperlink to a document you wish the other
party to see. This feature has now been adopted by the ITU as a working
document (AVD-2905) which hopefully will be standardised in the near
future.
RegPrior
Registration Priority & PreEmption RPP (or follow me) allows many
devices to share the same registration and you can assigned a priority
(0-9 9 being the highest) to each devices. The device with the highest
priority is granted registration and any lower priority registration are
automatically unregistered. The unregistered device is notified and
will continues to try and register (without success) until the
higher priority device unregisters and then regains the registration. For
Devices with the same priority, the new registration is prompted whether
to preempt the previous registration, if agreed the old registration is
preempted. I have also checked in the Gatekeeper support for this feature
into the GnuGk CVS.
PDI
Personal Data Interchange. Allows parties during a call setup to exchange
personal information (via vCard ; RFC2426) which contain extended
personal information and an up to 64x64 pixel image which can be used to
display on the other parties display. Each parties vCard is assigned a
GUID and in the call setup, this information is used with the lastupdate
value to determine whether to exchange new or update the current stored
vCard information. This information can then be exported to outlook or
any other program that supports vCard.
Hopefully these features will make their way through the ITU and be
adopted as standard H.460.x features.
If anybody has any questions, I would be happy to explain more on the
H.460 framework implementation or any particular feature.
Simon |
[1]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|