Topos and stun

Servan Kroes via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <[email protected]>
Hi,

We have implemented topos successfully. Only now we get an error in the log by receiving stun messages:
Jan  5 10:12:14 VC-POC-SERVAN kamailio@vcare_edgeudp[4163314]:  5(4163314) DEBUG: <core> [core/udp_server.c:741]: udp_rcv_loop(): probing packet received from 192.168.22.127 9601
Jan  5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]:  6(4163315) DEBUG: <core> [core/stun.c:42]: stun_process_msg(): STUN Message: [[>>>
Jan  5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]: <<<]]
Jan  5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]:  6(4163315) INFO: <core> [core/parser/parse_fline.c:145]: parse_first_line(): method not followed by SP
Jan  5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]:  6(4163315) ERROR: <core> [core/parser/parse_fline.c:274]: parse_first_line(): parse_first_line: bad message (offset: 0)
Jan  5 10:12:15 VC-POC-SERVAN kamailio@vcare_edgeudp[4163315]:  6(4163315) DEBUG: <core> [core/parser/msg_parser.c:721]: parse_msg(): invalid message
Jan  5 10:12:15 vm-kamailio kamailio[4163315]:  6(4163315) ERROR: <core> [core/parser/msg_parser.c:794]: parse_msg(): ERROR: parse_msg: message=<#001#001>
Jan  5 10:12:15 vm-kamailio kamailio[4163315]:  6(4163315) DEBUG: topos [topos_mod.c:446]: tps_prepare_msg(): outbuf buffer parsing failed!
Jan  5 10:12:15 vm-kamailio kamailio[4163316]:  7(4163316) DEBUG: <core> [core/udp_server.c:718]: udp_rcv_loop(): received on udp socket: (94/28/28) [[ 00  01  00  08  02  A6 P_ 97  1A  D8 , AE  CF  C8 c 06 u E6 7 00  03  00  04  00  00  00  04 ]]
Jan  5 10:12:15 vm-kamailio kamailio[4163316]:  7(4163316) DEBUG: <core> [core/stun.c:42]: stun_process_msg(): STUN Message: [[>>>
Jan  5 10:12:15 vm-kamailio kamailio[4163316]: <<<]]
Jan  5 10:12:15 vm-kamailio kamailio[4163316]:  7(4163316) INFO: <core> [core/parser/parse_fline.c:145]: parse_first_line(): method not followed by SP
Jan  5 10:12:15 vm-kamailio kamailio[4163316]:  7(4163316) ERROR: <core> [core/parser/parse_fline.c:274]: parse_first_line(): parse_first_line: bad message (offset: 0)
Jan  5 10:12:15 vm-kamailio kamailio[4163316]:  7(4163316) DEBUG: <core> [core/parser/msg_parser.c:721]: parse_msg(): invalid message
Jan  5 10:12:15 vm-kamailio kamailio[4163316]:  7(4163316) ERROR: <core> [core/parser/msg_parser.c:794]: parse_msg(): ERROR: parse_msg: message=<#001#001>
Jan  5 10:12:15 vm-kamailio kamailio[4163316]:  7(4163316) DEBUG: topos [topos_mod.c:446]: tps_prepare_msg(): outbuf buffer parsing failed!
Jan  5 10:12:15 vm-kamailio kamailio[4163317]:  8(4163317) DEBUG: <core> [core/udp_server.c:718]: udp_rcv_loop(): received on udp socket: (91/28/28) [[ 00  01  00  08  03  E0  EB N E6 A`Q C8 3 89 ~ D0  C9  E9 v 00  03  00  04  00  00  00  02 ]]
Jan  5 10:12:15 vm-kamailio kamailio[4163317]:  8(4163317) DEBUG: <core> [core/stun.c:42]: stun_process_msg(): STUN Message: [[>>>
Jan  5 10:12:15 vm-kamailio kamailio[4163317]: <<<]]
Jan  5 10:12:15 vm-kamailio kamailio[4163317]:  8(4163317) INFO: <core> [core/parser/parse_fline.c:145]: parse_first_line(): method not followed by SP
Jan  5 10:12:15 vm-kamailio kamailio[4163317]:  8(4163317) ERROR: <core> [core/parser/parse_fline.c:274]: parse_first_line(): parse_first_line: bad message (offset: 0)
Jan  5 10:12:15 vm-kamailio kamailio[4163317]:  8(4163317) DEBUG: <core> [core/parser/msg_parser.c:721]: parse_msg(): invalid message
Jan  5 10:12:15 vm-kamailio kamailio[4163317]:  8(4163317) ERROR: <core> [core/parser/msg_parser.c:794]: parse_msg(): ERROR: parse_msg: message=<#001#001>
Jan  5 10:12:15 vm-kamailio kamailio[4163317]:  8(4163317) DEBUG: topos [topos_mod.c:446]: tps_prepare_msg(): outbuf buffer parsing failed!

If we disable topos, we don't get these messages.

Is this an bug? Or is there a setting in topos or stun that I can check?

Kind regards,

Servan Kroes
__________________________________________________________
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.