Msg.execute: Difference between revisions
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
'''callto''' | '''callto''' | ||
::: | :::the module and module-specific address that is expected (by means of the routing decision) to service the call | ||
'''called''' | '''called''' | ||
::: | :::the number of the called | ||
'''called_instance''' | '''called_instance''' | ||
::: | :::the called instance | ||
'''caller''' | '''caller''' | ||
::: | :::the number of the caller | ||
'''caller_instance''' | '''caller_instance''' | ||
::: | :::he caller instance | ||
===How it works?=== | ===How it works?=== | ||
Revision as of 16:54, 22 January 2013
msg.execute is emitted by a module that wants to send a chat message.
Parameters
callto
- the module and module-specific address that is expected (by means of the routing decision) to service the call
called
- the number of the called
called_instance
- the called instance
caller
- the number of the caller
caller_instance
- he caller instance
How it works?
The module that handles msg.execute will check the callto parameter and called parameter to not be empty and if a full JID is obtain with a resource and a chan.text is emitted from the channel. The return value is true if the chan.text was emitted.
See also