The pua_dialoginfo retrieves dialog state information from the dialog module and PUBLISHes the dialog-information using the pua module. Thus, in combination with the presence_xml module this can be used to derive dialog-info from the dialog module and NOTIFY the subscribed watchers about dialog-info changes. This can be used for example with SNOM and Linksys phones. Note: This implements dialog-info according to RFC 4235 and is not compatible with the BLA feature defined in draft-anil-sipping-bla-03.txt. (Actually the BLA draft is really crap as it changes SIP semantics) The module is based on code (copy/paste) from pua_usrloc and nat_traversal module. Following you will show some examples of a dialog-info XML document taken from RFC 4235. This will help you to understand the meaning of the module parameters: <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="1" state="full" entity="sip:alice@example.com"> <dialog id="as7d900as8" call-id="a84b4c76e66710" local-tag="1928301774" remote-tag="456887766" direction="initiator"> <state>early</state> </dialog> </dialog-info> The root element is the "dialog-info". It contains the namespace, the version (which must be incremented for each new PUBLISH for this certain dialog), the state (this module only supports state=full) and the entity for which we publish the dialog-info. The "dialog" element must contain an id parameter. The id parameter is usually different to the optional call-id parameter (wh
Copyright © 2006 Voice Sistem SRL
Copyright © 2008 Klaus Darilion IPCom
Copyright © 2021 MomentTech
Copyright © 2024 Sipwise
