404 sent from Kamailio NOT from the script

Richard Robson via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <[email protected]>
I have a problem where a call comes in and causing a 404 Not Found to be 
replied.

the script does not have a 404 reply set in it anywhere

unfortunately I cannot get the script to produce logs, hence my other 
post. But its making it tricky to find the source of the 404. following 
the script it should not be producing a 404, but doing a relay. I 
suspect there is something wrong with the tm or its not getting a result 
it needs.

It looks like the transaction module is triggering thge 404 somehow and 
Its showing up in debug below.

Does anyone have any ideas why i'm getting a 404?

version 5.6.6

Regards, Richard

Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:1100]: t_check_msg(): msg (0x7faf977b64b0) id=4/28700 global 
id=3/28700 T start=0xffffffffffffffff
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:503]: t_lookup_request(): start searching: hash=60776, isACK=0
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:463]: matching_3261(): RFC3261 transaction matching failed - 
via branch [z9hG4bK-2e6a90ab-1bfb9be-d4ed8e5d-7f0300025430]
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:703]: t_lookup_request(): no transaction found
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:1172]: t_check_msg(): msg (0x7faf977b64b0) id=4/28700 global 
id=4/28700 T end=(nil)
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:1394]: t_newtran(): msg (0x7faf977b64b0) id=4/28700 global 
id=4/28700 T start=(nil)
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:503]: t_lookup_request(): start searching: hash=60776, isACK=0
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:463]: matching_3261(): RFC3261 transaction matching failed - 
via branch [z9hG4bK-2e6a90ab-1bfb9be-d4ed8e5d-7f0300025430]
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:703]: t_lookup_request(): no transaction found
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> 
[core/mem/q_malloc.c:385]: qm_malloc(): qm_malloc(0x7faf9301f000, 8336) 
called from tm: h_table.c: build_cell(336)
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_hooks.c:342]: run_reqin_callbacks_internal(): trans=0x7faf932f42c0, 
callback type 1, id 0 entered
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> 
[core/mem/q_malloc.c:385]: qm_malloc(): qm_malloc(0x7faf9301f000, 40) 
called from tm: t_hooks.c: insert_tmcb(134)
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:1100]: t_check_msg(): msg (0x7faf977b64b0) id=4/28700 global 
id=4/28700 T start=0x7faf932f42c0
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_lookup.c:1176]: t_check_msg(): T (0x7faf932f42c0) already found for 
msg (0x7faf977b64b0)!
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> 
[core/mem/q_malloc.c:385]: qm_malloc(): qm_malloc(0x7faf9301f000, 626) 
called from tm: t_reply.c: _reply_light(488)
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_reply.c:1768]: cleanup_uac_timers(): RETR/FR timers reset
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_hooks.c:252]: run_trans_callbacks_internal(): DBG: 
trans=0x7faf932f42c0, callback type 512, id 0 entered
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} acc 
[acc_logic.c:721]: tmcb_func(): acc callback called for 
t(0x7faf932f42c0) event type 512, reply code 404
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_reply.c:625]: _reply_light(): reply sent out - buf=0x7faf977bf7f8: 
SIP/2.0 404 Not Foun... shmem=0x7faf932f0468: SIP/2.0 404 Not Foun
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_funcs.c:122]: put_on_wait(): put T [0x7faf932f42c0] on wait
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} <core> 
[core/mem/q_malloc.c:495]: qm_free(): qm_free(0x7faf976b5010, 
0x7faf977bf7f8), called from tm: t_reply.c: _reply_light(635)
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} tm 
[t_reply.c:636]: _reply_light(): finished
Apr 22 14:50:51 kamai01 kamailio[28700]: DEBUG: {1 1 INVITE 
afc0c04-9d8bc3d-1bfb9be-7f02f033b5f0-2406050a-13d8-7225} sl [sl.c:288]: 
send_reply(): reply in stateful mode (tm)


__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.