Hi, yes you should switch to cvs version... cvs version should be stable as 1.3.2
Rodrigo A. Cremaschi wrote: > > Hi list, > > Kannel 1.3.2 panics after trying to send a message with source_addr: NULL, > destination_addr: NULL and sequence_number=0 > I have seen this issue reported earlier. I'm in production state. Should I > move to CVS? > This happens randomly with (as far as I know) two of my SMSC's. > > > Thanks. > > 2004-09-09 13:17:21 [11753] [8] DEBUG: SMPP[UNIFON]: Got PDU: > 2004-09-09 13:17:21 [11753] [8] DEBUG: SMPP PDU 0x8188200 dump: > 2004-09-09 13:17:21 [11753] [8] DEBUG: type_name: deliver_sm > 2004-09-09 13:17:21 [11753] [8] DEBUG: command_id: 5 = 0x00000005 > 2004-09-09 13:17:21 [11753] [8] DEBUG: command_status: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: sequence_number: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: service_type: NULL > 2004-09-09 13:17:21 [11753] [8] DEBUG: source_addr_ton: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: source_addr_npi: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: source_addr: NULL > 2004-09-09 13:17:21 [11753] [8] DEBUG: dest_addr_ton: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: dest_addr_npi: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: destination_addr: NULL > 2004-09-09 13:17:21 [11753] [8] DEBUG: esm_class: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: protocol_id: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: priority_flag: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: schedule_delivery_time: NULL > 2004-09-09 13:17:21 [11753] [8] DEBUG: validity_period: NULL > 2004-09-09 13:17:21 [11753] [8] DEBUG: registered_delivery: 0 = > 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: replace_if_present_flag: 0 = > 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: data_coding: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: sm_default_msg_id: 0 = 0x00000000 > 2004-09-09 13:17:21 [11753] [8] DEBUG: sm_length: 99 = 0x00000063 > 2004-09-09 13:17:21 [11753] [8] DEBUG: short_message: > 2004-09-09 13:17:21 [11753] [8] DEBUG: Octet string at 0x81a28e0: > 2004-09-09 13:17:21 [11753] [8] DEBUG: len: 99 > 2004-09-09 13:17:21 [11753] [8] DEBUG: size: 100 > 2004-09-09 13:17:21 [11753] [8] DEBUG: immutable: 0 > 2004-09-09 13:17:21 [11753] [8] DEBUG: data: 45 6e 20 63 75 61 6c 20 > 64 > 65 20 6c 61 73 20 73 En cual de las s > 2004-09-09 13:17:21 [11753] [8] DEBUG: data: 69 67 75 69 65 6e 74 65 > 73 > 20 64 69 73 63 69 70 iguientes discip > 2004-09-09 13:17:21 [11753] [8] DEBUG: data: 6c 69 6e 61 73 20 6e 6f > 20 > 73 65 20 6f 74 6f 72 linas no se otor > 2004-09-09 13:17:21 [11753] [8] DEBUG: data: 67 61 20 65 6c 20 50 72 > 65 > 6d 69 6f 20 4e 6f 62 ga el Premio Nob > 2004-09-09 13:17:21 [11753] [8] DEBUG: data: 65 6c 3f 20 46 2d 46 69 > 73 > 69 63 61 2f 50 2d 50 el? F-Fisica/P-P > 2004-09-09 13:17:21 [11753] [8] DEBUG: data: 65 72 69 6f 64 69 73 6d > 6f > 2f 51 2d 51 75 69 6d eriodismo/Q-Quim > 2004-09-09 13:17:21 [11753] [8] DEBUG: data: 69 63 61 > ica > 2004-09-09 13:17:21 [11753] [8] DEBUG: Octet string dump ends. > 2004-09-09 13:17:21 [11753] [8] DEBUG: SMPP PDU dump ends. > 2004-09-09 13:17:21 [11753] [8] PANIC: gwlib/octstr.c:2326: > seems_valid_real: Assertion `ostr != NULL' failed. (Called from gw > lib/octstr.c:807:octstr_check_range.) > > > Este mensaje se dirige exclusivamente a su destinatario y puede contener > informaci�n CONFIDENCIAL sometida a secreto profesional o cuya divulgaci�n > est� prohibida en virtud de la legislaci�n vigente. Si ha recibido este > mensaje por error, le rogamos que nos lo comunique inmediatamente por esta > misma v�a o por tel�fono (54.11 5776-5000) y proceda a su destrucci�n. > N�tese que el correo electr�nico v�a Internet no permite asegurar ni la > confidencialidad de los mensajes que se transmiten ni la correcta > recepci�n de los mismos. En caso de que el destinatario de este mensaje no > consintiera la utilizaci�n de correo electr�nico v�a Internet rogamos lo > ponga en nuestro conocimiento de manera inmediata. -- Thanks, Alex
