Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
Hello,
you can reorganize the config in order to execute t_relay() for ACK, then you
can do your stuff after it.
if is ack {
t_relay();
custom stuff
exit;
}
Cheers,
n relayed?
>
>
> Thanks
>
>
> Jon
>
>
>
>
> *From:* Daniel-Constantin Mierla <mico...@gmail.com>
> *Sent:* 05 December 2016 13:54
> *To:* Jonathan Hunter; Kamailio SER - Users Mailing List
> *Subj
relayed?
Thanks
Jon
From: Daniel-Constantin Mierla <mico...@gmail.com>
Sent: 05 December 2016 13:54
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
->
>
>
> So in effect RELAY the ACK, then trigger this SIP INFO to be sent?
>
>
> Thanks
>
>
> Jon
>
>
>
>
>
> *From:* Daniel-Constantin Mierla <mico...@gmail.com>
> *Sent:*
Thanks
Jon
From: Daniel-Constantin Mierla <mico...@gmail.com>
Sent: 05 December 2016 10:32
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
Hello,
all the headers must be in a sing
ing the command?
>
>
> Thanks
>
>
> Jon
>
>
>
>
> *From:* sr-users <sr-users-boun...@lists.sip-router.org> on behalf of
> Jonathan Hunter <hunter...@hotmail.com>
> *Sent:* 01 December 2016 16:12
> *To:* Kamailio SER - Users Mailing List; mico...@gmail
Hello,
all the headers must be in a single parameter, I see that you provide
headers one by one in the params array. Try:
jsonrpc_exec('
{
"jsonrpc":"2.0",
"method":"tm.t_uac_start",
"params": [
"INFO",
"$dlg(to_uri)",
".",
".",
From: sr-users <sr-users-boun...@lists.sip-router.org> on behalf of Jonathan
Hunter <hunter...@hotmail.com>
Sent: 01 December 2016 16:12
To: Kamailio SER - Users Mailing List; mico...@gmail.com
Subject: Re: [SR-Users] Send SIP Info within a dialog usi
Hi Daniel,
I am trying tm.t_uac_start and its stating Content-Type Missing, I have tried
to add to params but it doesnt like it, where should it be defined?
Command below;
jsonrpc_exec('{"jsonrpc":"2.0","method":"tm.t_uac_start","params": ["INFO",
December 2016 12:24
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
Hello,
are you still trying with MI command via kamctl? Not with the jsonrpc-s module
and tm.t_uac_start?
When dou
--
> *From:* Daniel-Constantin Mierla <mico...@gmail.com>
> *Sent:* 01 December 2016 12:24
> *To:* Jonathan Hunter; Kamailio SER - Users Mailing List
> *Subject:* Re: [SR-Users] Send SIP Info within a dialog using
> $uac_req(method)="INFO"
>
>
> Hello,
>
From: Daniel-Constantin Mierla <mico...@gmail.com>
Sent: 01 December 2016 12:24
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
Hello,
are you still trying with MI co
STOP"\r\n\""
>
>
> Can you tell me how I can escape " so its actually within the SIP
> header itself?
>
> Many thanks
>
> Jon
>
>
>
> ------------------------
> *From:* sr-users <sr-user
" so its actually within the SIP header itself?
Many thanks
Jon
From: sr-users <sr-users-boun...@lists.sip-router.org> on behalf of Jonathan
Hunter <hunter...@hotmail.com>
Sent: 25 November 2016 18:55
To: Kamailio SER - Users Mailing List; mic
8
To:sip:3003@193.144.1.112
Contact:sip:daemon@8.8.8.8
"
Thanks
Jon
From: Daniel-Constantin Mierla <mico...@gmail.com><mailto:mico...@gmail.com>
Sent: 22 November 2016 13:10
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send
gt;>>
>>> And still get invalid socket, as it is including all the SIP headers
>>> in with the port parameter so I presume I am missing an operator?
>>>
>>>
>>> /usr/sbin/kamailio[28999]: ERROR: [main.c:1128]:
>>> parse_phostport(): too ma
003@193.144.1.112
Contact:sip:daemon@8.8.8.8
"
Thanks
Jon
From: Daniel-Constantin Mierla <mico...@gmail.com>
Sent: 22 November 2016 13:10
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
in
>> udp:10.70.1.136:5060From:sip:1234@8.8.8.8rnTo:sip:3003@193.144.1.112rnContact:sip:daemon@8.8.8.8rn'
>>
>>
>>
>> Its including them all as the local socket/port.
>>
>> Thanks
>>
>> Jon
>>
>> --
Hello,
One last question relating to this issue of sending SIP INFO within a dialog.
(Sorry!)
As you know I now have t_uac_dlg working with the exec module to create the SIP
INFO, however how do I inject it effectively within the dialog?
I have added event_route[dialog:start] as thought
hem all as the local socket/port.
Thanks
Jon
From: Daniel-Constantin Mierla <mico...@gmail.com><mailto:mico...@gmail.com>
Sent: 21 November 2016 11:29
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within
> *From:* Daniel-Constantin Mierla <mico...@gmail.com>
> *Sent:* 21 November 2016 11:29
> *To:* Jonathan Hunter; Kamailio SER - Users Mailing List
> *Subject:* Re: [SR-Users] Send SIP Info within a dialog using
> $uac_req(method)="
m><mailto:mico...@gmail.com>
Sent: 17 November 2016 09:43
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
Hello,
just to point out a trick that sometime can save backslash escaping
;
>
> Thanks
>
> Jon
>
>
> ------------------------
> *From:* Daniel-Constantin Mierla <mico...@gmail.com>
> *Sent:* 17 November 2016 09:43
> *To:* Jonathan Hunter; Kamailio SER - Users Mailing List
> *Subject:* Re:
y colons in
udp:10.70.1.136:5060"From:sip:1234@8.8.8.8
Thanks
Jon
From: Daniel-Constantin Mierla <mico...@gmail.com>
Sent: 17 November 2016 09:43
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$u
>
> *From:* sr-users <sr-users-boun...@lists.sip-router.org> on behalf of
> Jonathan Hunter <hunter...@hotmail.com>
> *Sent:* 16 November 2016 12:06
> *To:* Kamailio SER - Users Mailing List; mico...@gmail.c
16 12:06
To: Kamailio SER - Users Mailing List; mico...@gmail.com
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
Hello Daniel,
Sorry to bother you again, last time!
So the mi command line is;
kamctl mi t_uac_dlg INFO sip:3003@193.144.1.112
9:45
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
Hello,
as I can see in the logs, the rpc command fails to execute because it requires
async processing which is not implemented by jsonrp
r 2016 09:45
To: Jonathan Hunter; Kamailio SER - Users Mailingh List
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
Hello,
as I can see in the logs, the rpc command fails to execute because it requires
async processing which is not implemented by
Hello,
as I can see in the logs, the rpc command fails to execute because it
requires async processing which is not implemented by jsonrpc-s module.
Then it is an INVITE received:
ct 7 13:45:36 POC_ProxyA /usr/sbin/kamailio[6572]: INFO:
Hello,
Please see debug output for when I try and send the SIP INFO when I am
initiating a new call.
I am just testing out the command currently, in practice I will look to inject
the SIP INFO into an already formed dialog, so is the way I am trying to test
cause me an issue?
I can see;
rrectly) you can get the command to overwrite
> the current contents of the headers, so as above the RURI would change
> to sip:3003@8.8.8.8 and the From to sip:1234@2.2.2.2 etc, however they
> remain unchanged.
>
> Does that make sense?
>
> Thanks
>
> Jon
>
>
>
>
>
>
> ---
;,".","From:sip:1234@2.2.2.2","To:sip:3003@8.8.8.8","Contact:sip:1234@2.2.2.2"]}');
All I see it fire is an INFO message to Request-Line: INFO sip:kamailio.org
SIP/2.0, with default parameters.
Thanks
Jon
From:
ot;,".",".","From:sip:1234@2.2.2.2","To:sip:3003@8.8.8.8","Contact:sip:1234@2.2.2.2"]}');
>
> All I see it fire is an INFO message to Request-Line: INFO
> sip:kamailio.org SIP/2.0, with default parameters.
>
>
> Thanks
>
>
> Jon
>
>
> -
);
All I see it fire is an INFO message to Request-Line: INFO sip:kamailio.org
SIP/2.0, with default parameters.
Thanks
Jon
From: Daniel-Constantin Mierla <mico...@gmail.com>
Sent: 15 November 2016 08:03
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-
144.1.112","Contact:sip:daemon@8.8.8.8"]}]]
>
> Can you give me some clues on how to input the params as its not clear
> to me from kamailio or json rpc docs.
>
>
>
> Many thanks
>
> Jon
>
>
>
>
> -
put the params as its not clear to me
from kamailio or json rpc docs.
Many thanks
Jon
____
From: Daniel-Constantin Mierla <mico...@gmail.com>
Sent: 17 October 2016 09:45
To: Jonathan Hunter; Kamailio SER - Users Mailing List
Subject: Re: [SR-Users] Send SI
-------
> To: sr-users@lists.sip-router.org
> From: mico...@gmail.com
> Date: Thu, 6 Oct 2016 12:41:32 +0200
> Subject: Re: [SR-Users] Send SIP Info within a dialog using
> $uac_req(method)="INFO"
>
> Hello,
> uac_req_send() i
I
doing wrong with the syntax?
Thanks
Jon
From: hunter...@hotmail.com
To: mico...@gmail.com; sr-users@lists.sip-router.org
Date: Fri, 14 Oct 2016 08:52:25 +
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="INFO"
Hi Daniel,
Thanks for the response, so
looking to modify in a B2BUA rather than the proxy, or will the dialog
module handle this?
Thanks
Jon
To: sr-users@lists.sip-router.org
From: mico...@gmail.com
Date: Thu, 6 Oct 2016 12:41:32 +0200
Subject: Re: [SR-Users] Send SIP Info within a dialog using
$uac_req(method)="
Hello,
uac_req_send() is able to send only initial requests (with follow up on
auth challenge). It doesn't expose the ability to send requests within a
dialog -- the functions exist in c (tm module), but not availble in config.
On the other hand, there should be a mi/rpc command exported by tm
Hi Guys,
Is it still the case that when using uac_req_send, you cant send withing a
specific dialog?I can modify call-id, but I presume tags may be more of a
problem?See old post below from 2015;
> I am familiar with uac_req_send. but how do I send it with in a
> specific dialog and with data in
41 matches
Mail list logo