[sr-dev] [kamailio/kamailio] Commande tm.t_uac_start issue (#1393)
JuanPascual2
notifications at github.com
Wed Jan 10 10:30:43 CET 2018
Commande tm._uac_start JsonRPC with Headers From, To and Fake works
{"id":1,"jsonrpc":"2.0","method":"tm.t_uac_start","params":["REGISTER","sip:suio.com","sip:101.155.139.171:5060","udp:10.155.139.170:5064","From:sip:juan at sui.com\r\nTo:sip:juan at sui.com\r\nFake:hedear\r\n"]}
{
"jsonrpc": "2.0",
"result": {
},
"id": 1
}
But commande tm.t_uac_start JsonRPC with only Headers From and To doesn't works
{"id":1,"jsonrpc":"2.0","method":"tm.t_uac_start","params":["REGISTER","sip:suio.com","sip:101.155.139.171:5060","udp:10.155.139.170:5064","From:sip:juan at sui.com\r\nTo:sip:juan at sui.com\r\n"]}
{
"jsonrpc": "2.0",
"error": {
"code": 500,
"message": "out of memory"
},
"id": 1
}
On documentation module tm, only From and To headers are mandatories.
5. RPC Commands
5.1. tm.t_uac_start
Generates and sends a local SIP request.
Parameters:
method - request method
RURI - request SIP URI
NEXT HOP - next hop SIP URI (OBP); use “.” if no value.
socket - local socket to be used for sending the request; use “.” if no value.
headers - set of additional headers to be added to the request; at least “From” and “To” headers must be provided)
body - (optional, may not be present) request body (if present, requires the “Content-Type” and “Content-length” headers)
Best regard
Juan
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1393
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20180110/fed64263/attachment.html>
More information about the sr-dev
mailing list