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@sui.com\r\nTo:sip:juan@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","…
[View More]params":["REGISTER","sip:suio.com","sip:101.155.139.171:5060","udp:10.155.139.170:5064","From:sip:juan@sui.com\r\nTo:sip:juan@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
[View Less]
Hi all,
I've to develop a module that uses cdp to contact an HSS. To understand how
to use cdp API I'm looking into other modules that already use it. Of
course, I read also the module documentation.
Looking into ims-registrar-scscf I found something that triggers my
curiosity. My question is about this
https://github.com/kamailio/kamailio/blob/master/src/modules/ims_registrar_…
The effect of that part is that the callback is going to be added only
once. In that case, why bother with the …
[View More]lock and the shared variable when
the initialisation could be done in mod_init()?
If someone can answer it I would be really grateful.
Cheers,
Alfonso.
[View Less]
Module: kamailio
Branch: master
Commit: d1f1b08e757955158b73841f344b993d52b26d29
URL: https://github.com/kamailio/kamailio/commit/d1f1b08e757955158b73841f344b993…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2018-01-16T09:01:41+01:00
modules: readme files regenerated - topos ... [skip ci]
---
Modified: src/modules/topos/README
---
Diff: https://github.com/kamailio/kamailio/commit/d1f1b08e757955158b73841f344b993……
[View More]
Patch: https://github.com/kamailio/kamailio/commit/d1f1b08e757955158b73841f344b993…
---
diff --git a/src/modules/topos/README b/src/modules/topos/README
index cf4bce61f6..c921117131 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -84,7 +84,10 @@ Chapter 1. Admin Guide
The module is transparent for the configuration writer. It only needs
to be loaded (tune the parameters if needed).
- It works for SIP MESSAGE requests.
+ It also works for SIP MESSAGE or other requests that do not create a
+ call dialog -- record_route() must be used for them as well, the
+ headers are not going to be in the messages sent to the network, they
+ are needed to know local addresses used to communicate with each side.
2. Dependencies
@@ -95,7 +98,8 @@ Chapter 1. Admin Guide
The following modules must be loaded before this module:
* rr module - server must perform record routing to ensure in-dialog
- requests are encoded/decoded.
+ requests are encoded/decoded (it must be done for all initial
+ requests).
* database module - to store the data for topology stripping and
restoring.
[View Less]
Module: kamailio
Branch: master
Commit: 4e659b5f3cd9b176e3bf2e20ceebf34d9734707b
URL: https://github.com/kamailio/kamailio/commit/4e659b5f3cd9b176e3bf2e20ceebf34…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2018-01-16T08:46:39+01:00
topos: docs - more explicit info about required use of record_route()
---
Modified: src/modules/topos/doc/topos_admin.xml
---
Diff: https://github.com/kamailio/kamailio/…
[View More]commit/4e659b5f3cd9b176e3bf2e20ceebf34…
Patch: https://github.com/kamailio/kamailio/commit/4e659b5f3cd9b176e3bf2e20ceebf34…
---
diff --git a/src/modules/topos/doc/topos_admin.xml b/src/modules/topos/doc/topos_admin.xml
index bda8ab766d..3320bf3642 100644
--- a/src/modules/topos/doc/topos_admin.xml
+++ b/src/modules/topos/doc/topos_admin.xml
@@ -26,7 +26,10 @@
loaded (tune the parameters if needed).
</para>
<para>
- It works for SIP MESSAGE requests.
+ It also works for SIP MESSAGE or other requests that do not create
+ a call dialog -- record_route() must be used for them as well, the
+ headers are not going to be in the messages sent to the network, they
+ are needed to know local addresses used to communicate with each side.
</para>
</section>
<section>
@@ -39,7 +42,8 @@
<listitem>
<para>
<emphasis>rr module</emphasis> - server must perform record
- routing to ensure in-dialog requests are encoded/decoded.
+ routing to ensure in-dialog requests are encoded/decoded (it
+ must be done for all initial requests).
</para>
</listitem>
<listitem>
[View Less]