Hello,
I'm attaching more logs to this email regarding to the issue on SIP
CANCEL to an INVITE that is suspended.
If do you think that i should open an issue on git regarding to this let me
know.
Thank you for your help.
Best Regards
José
2016-06-15 14:42 GMT+01:00 José Seabra <joseseab...@gmail.com>:
> Hi Daniel,
>
> But when Kamailio receives a CANCEL prints the following error messages:
>
> 2016-06-15 14:39:10.354 ERROR: tm [t_msgbuilder.c:287]:
> build_local_reparse(): ERROR: build_local_reparse: INVITE is missing
> 2016-06-15 14:39:10.354 ERROR: tm [t_msgbuilder.c:494]:
> build_local_reparse(): ERROR: build_local_reparse: cannot build CANCEL
> request
> 2016-06-15 14:39:10.354 ERROR: tm [t_cancel.c:310]: cancel_branch():
> ERROR: attempt to build a CANCEL failed
> 2016-06-15 14:39:10.354 ERROR: tm [t_fwd.c:1389]: e2e_cancel(): ERROR:
> cancel error
>
> I'm handling the CANCEL in the script by the following way:
>
>
> if (is_method("CANCEL")) {
> if (t_check_trans()) {
> route(RELAY);
> } else {
> sl_send_reply("481", "Call leg/transaction does
> not exist");
> }
> exit();
> ...
> ...
> ...
>
> Thank you for your support.
>
> Regards
> José
>
>
> 2016-06-15 12:15 GMT+01:00 Daniel-Constantin Mierla <mico...@gmail.com>:
>
>> Hello,
>>
>> On 14/06/16 16:33, José Seabra wrote:
>>
>> Hi Olle and Daniel,
>> Thank you for your replies, After receive your msg I looked again to my
>> script and i found the problem.
>>
>> I didn't configure the correct failure_route block and the failure route
>> configured didn't print any msg on the logs, so I thought that it wasn't
>> entering on failure route.
>>
>> Sorry for my mistake.
>>
>> Anyway, How should i handle the CANCEL sip msg to an INVITE that is
>> suspended? (still related with this implementation)
>>
>> Just handling it as done in the default configuration file is ok -- the
>> suspended transaction will be canceled.
>>
>> Cheers,
>> Daniel
>>
>>
>>
>> Thank you for your support.
>>
>> Regards
>>
>> 2016-06-14 14:52 GMT+01:00 Olle E. Johansson <o...@edvina.net>:
>>
>>>
>>> On 14 Jun 2016, at 15:45, José Seabra < <joseseab...@gmail.com>
>>> joseseab...@gmail.com> wrote:
>>>
>>> Hello,
>>>
>>> Regarding to this implementation, I'm sending SIP Subscribe message from
>>> uac_req_send function to CNAM server but it is unavailable and Kamailio
>>> doesn't receive any reply from CNAM server, What I'm noticing is that
>>> kamailio is retransmitting the SIP Subscribe msg until get "408 request
>>> time out".
>>>
>>> In order to implement a failure_route to this SIP Subscribe msg sent
>>> from uac_req_send I put kamailio send this SIP msg first to itself then
>>> kamailio set the failure_route and send SIP Subscribe msg to CNAM server
>>> using t_relay from script configuration file, but kamailio still not
>>> entering on failure_route block.
>>>
>>> I am doing the same with SIP REGISTER and get into the failure route
>>> with a lot of different issues. Haven’t specifically tried with a local TM
>>> timeout, a locally generated 408 though.
>>>
>>>
>>> How can I set failure_route to this SIP Subscribe msg sent from
>>> uac_req_send()
>>>
>>> SHould work with a normal failure route trigger in the script.
>>>
>>> Sounds very strange ...
>>>
>>> /O
>>>
>>>
>>> Regards
>>>
>>> 2016-06-07 22:06 GMT+01:00 José Seabra < <joseseab...@gmail.com>
>>> joseseab...@gmail.com>:
>>>
>>>> Hello,
>>>>
>>>> Thank you for the feedback.
>>>>
>>>> BR
>>>>
>>>> 2016-06-07 8:38 GMT+01:00 Pavel Eremin < <eremina....@gmail.com>
>>>> eremina....@gmail.com>:
>>>>
>>>>> Hi,
>>>>>
>>>>> We using PERL moodule and PERL script to do this.
>>>>> Don't sure but, Kamailio will stop anyway when it sends www query and
>>>>> wating answer.
>>>>>
>>>>>
>>>>> 2016-06-06 19:56 GMT+05:00 José Seabra < <joseseab...@gmail.com>
>>>>> joseseab...@gmail.com>:
>>>>>
>>>>>> Hello there,
>>>>>> I need to use kamailio to consult an CNAM server in order to get the
>>>>>> caller id name and number to the call, the diagram bellow represents
>>>>>> what i
>>>>>> need implement:
>>>>>>
>>>>>> <kamailio_CNAM.png>
>>>>>>
>>>>>>
>>>>>> Can I implement this behavior through the following kamailio modules:
>>>>>>
>>>>>> 1. tm and tmx module (call the function t_suspend and t_continue
>>>>>> in order to stop INVITE transaction and resume it).
>>>>>> 2. UAC module (generate the SUBSCRIBE sip message)
>>>>>> 3. Some kamailio scripting logic to manage this behavior.
>>>>>>
>>>>>> what are your advices to implement this scenario?
>>>>>>
>>>>>> Thank you for your help
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cumprimentos
>>>>>> José Seabra
>>>>>>
>>>>>> _______________________________________________
>>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>>>>>> list
>>>>>> sr-users@lists.sip-router.org
>>>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>>>> sr-users@lists.sip-router.org
>>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Cumprimentos
>>>> José Seabra
>>>>
>>>
>>>
>>>
>>> --
>>> Cumprimentos
>>> José Seabra
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users@lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users@lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>
>>
>> --
>> Cumprimentos
>> José Seabra
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>> --
>> Daniel-Constantin Mierlahttp://www.asipto.com -
>> http://www.kamailio.orghttp://twitter.com/#!/miconda -
>> http://www.linkedin.com/in/miconda
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
>
> --
> Cumprimentos
> José Seabra
>
--
Cumprimentos
José Seabra
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} INFO: <script>: New
request - M=CANCEL R=sip:sec.abcsoft.503@example.local F=sip:502@example.local
T=sip:sec.abcsoft.503@example.local IP=udp:10.112.185.128:5060
ID=4mi9eNbuolumfFpoy0b0jw
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: siputils
[checks.c:97]: has_totag(): no totag
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:701]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: searching on
hash entry 54310
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:409]: matching_3261(): DEBUG: RFC3261 transaction matched,
tid=yP9-Om7uwsXsEVKU1ArX0Q
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:798]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: canceled
transaction found (0x7f476dd67c38)!
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:801]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT completed
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[tm.c:992]: w_t_lookup_cancel(): lookup_original: t_lookupOriginalT returned:
0x7f476dd67c38
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:1312]: t_newtran(): DEBUG: t_newtran: msg id=7 , global msg id=6 ,
T on entrance=0xffffffffffffffff
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching:
hash=54310, isACK=0
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction
found
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_hooks.c:358]: run_reqin_callbacks_internal(): DBG: trans=0x7f476dd73078,
callback type 1, id 0 entered
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: <core>
[md5utils.c:67]: MD5StringArray(): MD5 calculated:
dcf75426037c4eae918870c6c53e4cd0
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:701]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: searching on
hash entry 54310
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:409]: matching_3261(): DEBUG: RFC3261 transaction matched,
tid=yP9-Om7uwsXsEVKU1ArX0Q
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:798]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: canceled
transaction found (0x7f476dd67c38)!
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_lookup.c:801]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT completed
2016-06-20 15:28:06.825 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} ERROR: tm
[t_msgbuilder.c:287]: build_local_reparse(): ERROR: build_local_reparse: INVITE
is missing
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} ERROR: tm
[t_msgbuilder.c:494]: build_local_reparse(): ERROR: build_local_reparse: cannot
build CANCEL request
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} ERROR: tm
[t_cancel.c:310]: cancel_branch(): ERROR: attempt to build a CANCEL failed
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} ERROR: tm
[t_fwd.c:1389]: e2e_cancel(): ERROR: cancel error
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_reply.c:1592]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR
timers reset
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_reply.c:648]: _reply_light(): DEBUG: reply sent out. buf=0x7f477191e2d0:
SIP/2.0 500 cancel e..., shmem=0x7f476dd72d08: SIP/2.0 500 cancel e
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_reply.c:658]: _reply_light(): DEBUG: _reply_light: finished
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: tm
[t_funcs.c:368]: t_relay_to(): SER: new transaction fwd'ed
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: <core>
[usr_avp.c:631]: destroy_avp_list(): destroying list (nil)
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: <core>
[usr_avp.c:631]: destroy_avp_list(): destroying list (nil)
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: <core>
[usr_avp.c:631]: destroy_avp_list(): destroying list (nil)
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: <core>
[usr_avp.c:631]: destroy_avp_list(): destroying list (nil)
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: <core>
[usr_avp.c:631]: destroy_avp_list(): destroying list (nil)
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: <core>
[usr_avp.c:631]: destroy_avp_list(): destroying list (nil)
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: <core>
[xavp.c:446]: xavp_destroy_list(): destroying xavp list (nil)
2016-06-20 15:28:06.826 {1 CANCEL 4mi9eNbuolumfFpoy0b0jw} DEBUG: <core>
[receive.c:322]: receive_msg(): cleaning up
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
