[SR-Users] Kamailio consult CNAM server through SIP Subscribe.

Daniel-Constantin Mierla miconda at gmail.com
Mon Jun 20 18:14:43 CEST 2016


Hello,

it seems it tries to generate an outgoing cancel for the suspended
branch. I will check the code, likely there has to be added condition
for this cases.

Is the 487 reply for invite sent back? Also, the 200ok for cancel?

Cheers,
Daniel


On 20/06/16 16:38, José Seabra wrote:
> 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 <joseseabra4 at gmail.com
> <mailto:joseseabra4 at 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
>     <miconda at gmail.com <mailto:miconda at 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 <oej at edvina.net
>>         <mailto:oej at edvina.net>>:
>>
>>
>>>             On 14 Jun 2016, at 15:45, José Seabra
>>>             <joseseabra4 at gmail.com <mailto:joseseabra4 at 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
>>>             <joseseabra4 at gmail.com <mailto:joseseabra4 at gmail.com>>:
>>>
>>>                 Hello, 
>>>
>>>                 Thank you for the feedback.
>>>
>>>                 BR
>>>
>>>                 2016-06-07 8:38 GMT+01:00 Pavel Eremin
>>>                 <eremina.net at gmail.com <mailto:eremina.net at 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
>>>                     <joseseabra4 at gmail.com
>>>                     <mailto:joseseabra4 at 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 at lists.sip-router.org
>>>                         <mailto:sr-users at 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 at lists.sip-router.org
>>>                     <mailto:sr-users at 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 at lists.sip-router.org
>>>             <mailto:sr-users at 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 at lists.sip-router.org
>>             <mailto:sr-users at 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 list
>>         sr-users at lists.sip-router.org
>>         <mailto:sr-users at lists.sip-router.org>
>>         http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>         -- Daniel-Constantin Mierla http://www.asipto.com -
>         http://www.kamailio.org http://twitter.com/#!/miconda
>         <http://twitter.com/#%21/miconda> -
>         http://www.linkedin.com/in/miconda
>
>
>         _______________________________________________
>         SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
>         mailing list
>         sr-users at lists.sip-router.org
>         <mailto:sr-users at lists.sip-router.org>
>         http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
>
>     -- 
>     Cumprimentos
>     José Seabra
>
>
>
>
> -- 
> Cumprimentos
> José Seabra

-- 
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.org
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160620/ee145e68/attachment.html>


More information about the sr-users mailing list