SIP Methods
(→Enable SUBSCRIBE Method) |
(→Additional methods) |
||
Line 9: | Line 9: | ||
===Additional methods=== | ===Additional methods=== | ||
− | Use section [methods] from [[SIP Configuration File|ysipchan.conf]] to allow/restrict the processing of specific SIP methods. For enabled methods yate will generate internal messages with name [[ | + | Use section [methods] from [[SIP Configuration File|ysipchan.conf]] to allow/restrict the processing of specific SIP methods. For enabled methods yate will generate internal messages with name [[SIP_Generic_Message|sip.<methodname>]] that can be handled from other modules. |
===Examples=== | ===Examples=== |
Revision as of 18:07, 8 November 2012
This page describes the Sip methods that are handled by default in Yate and how to enable the ones that are not generically handled.
Contents |
SIP Methods in Yate
Some standard SIP methods can be handled generically in Yate like INVITE, CANCEL, ACK, BYE, REFER, OPTIONS and REGISTER.
For example SIP method INFO in a dialog is handled internally by Yate but dialogless is handled generically (by using parameter lazy100 in ysipchan.conf).
Additional methods
Use section [methods] from ysipchan.conf to allow/restrict the processing of specific SIP methods. For enabled methods yate will generate internal messages with name sip.<methodname> that can be handled from other modules.
Examples
Enable MESSAGE Method
ysipchan.conf
[methods] message=yes
In regexroute.conf
[extra] sip.message=120 [sip.message] .*=echo Got SIP MESSAGE type '${xsip_type}' ${xsip_body_encoding} from '${username}': ${xsip_body}
Enable SUBSCRIBE Method
ysipchan.conf
[methods] subscribe=yes
You then configure the allowed events for subscribing in sipfeatures.conf and define the logic for SUBSCRIBE/NOTIFY in subscription.conf.
See also