SIP Features Module

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
(Implemented SIP Methods)
Line 12: Line 12:
 
  [methods]
 
  [methods]
 
  subscribe=yes
 
  subscribe=yes
 +
 +
To configure the logic of how to handle the subscriptions and the parameters from sipfeatures.conf use subscription.conf file.
  
 
=== Message handlers ===
 
=== Message handlers ===

Revision as of 17:38, 7 November 2012

This page describes the SIP features module.

Contents

Implemented SIP Methods

This module implements the following SIP methods:

  • SUBSCRIBE - Allow SIP clients to subscribe to specific events
  • NOTIFY - Notify SIP clients when an event's state changed

To enable the subscribe method set:

ysipchan.conf

[methods]
subscribe=yes

To configure the logic of how to handle the subscriptions and the parameters from sipfeatures.conf use subscription.conf file.

Message handlers

Internally Yate will handle the following messages:

Configuration file

sipfeatures.conf contains sections:

[general]

  • expires_min: int: Minimum allowed expiring time in seconds. Defaults to 60
  • expires_def: int: Default expiring time if not present in requests. Defaults to 600
  • expires_max: int: Value used to limit the expiring time to something sane. Defaults to 3600
  • forcedialogdata: boolean: Force (fill if missing) some parameters (dialog.callid, dialog.localtag, dialog.remotetag, dialog.remoteuri) in dialog state notification if made for a valid dialog (dialog.id is not empty). Defaults to enable.

[allow_events]

Restrict/allow subscriptions to individual events. If an event is disabled, no subscriptions to it will be allowed

  • default: boolean: Default value if an event is not listed here. Defaults to enable
  • dialog: boolean: Enable/disable subscriptions to dialog state events. Defaults to enable
  • message-summary: boolean: Enable/disable subscriptions to message waiting events. Defaults to enable


To configure the logic of how to handle the subscriptions and the parameters above use subscription.conf file.


Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers