Hi,

 

I’m creating a configuration is for a SIP <> HTTP gateway (performing protocol conversion) and thus all SIP messages and responses needs to be generated from the kamailio config file.

 

I’m failing to create the case where the calling user abandons the session, and thus, following the reception of a CANCEL a 200 “OK” needs to be sent to this transaction and later the 487 “Request Terminated” to the SIP INVITE original session.

 

On the traces I see:

SIP INVITE (Cseq 1 INVITE) -->

100 Trying (Cseq 1 INVITE) <--

180 Ringing (Cseq 1 INVITE) <--

SIP CANCEL (Cseq 1 CANCEL) -->

200 Ok (CSeq 1 CANCEL) <--

487 Request Terminated (CSeq 1 CANCEL)

 

Have then tried several options, trying to force the CSeq 1 INVITE but without success.

t_reply_callid("$ci", "$cs", "487", " Request Terminated ");

t_reply_callid("$ci", "$rm", "487", "Request Terminated");

t_reply_callid("$ci", "1", "487", "Request Terminated");

 

For instance, for the last I get the following log.

 6(60226) exec: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=705 a=28 n=t_reply_callid

 6(60226) DEBUG: tm [t_lookup.c:1715]: t_lookup_callid(): created comparable call_id header field: >Call-ID: 76589ZTJmNTAwZDhlOTZiM2I3MjhhYzllNjgyOWVjZGZmMzk

< 

 6(60226) DEBUG: tm [t_lookup.c:1719]: t_lookup_callid(): created comparable cseq header field: >CSeq: 1 INVITE<

 6(60226) DEBUG: tm [t_lookup.c:1722]: t_lookup_callid(): just locked hash index 18668, looking for transactions there:

 6(60226) DEBUG: tm [t_lookup.c:1749]: t_lookup_callid(): DEBUG: t_lookup_callid: transaction not found.

 6(60226) DEBUG: tmx [tmx_mod.c:500]: t_reply_callid(): Lookup failed - no transaction

 

Could you assist here?

 

Thanks,

Joao

 

 

 

Joao Alves

Solution Architect, Unified Communications

 

+351 214094660 (desk)

+351 912783702 (mobile)

 

AMDOCS | EMBRACE CHALLENGE EXPERIENCE SUCCESS

 

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp