Using SIP MESSAGE or how to enable chat messages in SIP
From Yate Documentation
(Difference between revisions)
(→501 Not Implemented) |
(→405 Method Not Allowed) |
||
Line 33: | Line 33: | ||
SIP/2.0 405 Method Not Allowed | SIP/2.0 405 Method Not Allowed | ||
+ | |||
+ | '''See also''' | ||
+ | * [[How to setup chat and short file transfer using MESSAGE Request Method|Using MESSAGE request method in older Yate versions]] | ||
+ | * [[Routing]] |
Revision as of 13:05, 25 October 2013
Starting with Yate 5 or svn revision 5629 yate changed the way it handles SIP MESSAGE request method.
You can now enable chat messages between SIP client much easier.
Contents |
Configuration
In ysipchan.conf section message set enable=yes.
[message] ; Controls the behaviour for SIP messaging ; enable: bool: Allow the SIP module to receive MESSAGE requests enable=yes ; auth_required: bool: Automatically challenge all senders for authentication ;auth_required=enable ; async_process: bool: Process SIP MESSAGE asynchronously in their own thread ;async_process=enable
How it works
When yate receives SIP MESSAGE request from user it will send a call.route message with route_type='msg'.
This message will be handled by the routing module. You won't need to make other configurations.
Debugging
501 Not Implemented
If you receive '501 Not Implemented' from Yate it means that you didn't set 'enable=yes' in message section or the Yate is too old and you need to install a newer version.
SIP/2.0 501 Not Implemented
405 Method Not Allowed
If you receive '405 Method Not Allowed' then the user you are trying to send a message to is offline.
SIP/2.0 405 Method Not Allowed
See also