Hi, Cyrus.

I've got same behavior in my server. And I don't have any VPN, so it's 
something else.
Have you found any fix for this. 

Regards,
M.


On Friday April 27 2007 11:28, Info wrote:
> It looks like some ports are not opened correctly? Or perhaps the needed 
> ports are still not release correctly by some thread of kannel in case of the 
> vpn issue?
> 
> Regards
> 
> -----Original Message-----
>     From: "Cyrus Patel"<[EMAIL PROTECTED]>
>     Sent: 26/04/07 05:20:44
>     To: "[email protected]"<[email protected]>
>     Subject: Kannel connection recovery issues
>       Hello,
>      
>     I'm having a strange issue with Kannel's recovery behaviour after the
>     connection to the SMSC goes down.
>      
>     I am connected to a SMSC over a VPN connection. Unfortunately for some
>     reason the VPN sometimes goes down and Kannel detects it and reconnects 
> and
>     can receive SMSs but not send them. The kannel status page shows the
>     outgoing messages queuing up: 
>      
>     SMS: received 130 (0 queued), sent 48 (10 queued), store size 10
>      
>     The strange thing is I tried doing the test where I pulled the network 
> cable
>     out and reconnected it and kannel recovers fine. Kannel only seems to be
>     stuck when the VPN goes down.
>      
>     Here is the sequence of events:
>      
>     1.    VPN goes down. Kannel detects this and tries to reconnect:
>      
>     2007-04-23 18:17:00 [2791] [7] ERROR:
>     SMPP[SMPP:********:5000/5000:****:*****]: No responses from SMSC within 
> 300
>     sec. Reconnecting.
>     2007-04-23 18:17:00 [2791] [7] ERROR:
>     SMPP[SMPP:********:5000/5000:****:*****]: Couldn't connect to SMS center
>     (retrying in 10 seconds).
>      
>     2.    Kannel successfully reconnects and the enquire links are responded 
> to
>     fine:
>      
>     2007-04-11 09:03:46 [9121] [7] DEBUG: SMPP PDU 0x86c40b0 dump:
>     2007-04-11 09:03:46 [9121] [7] DEBUG:   type_name: enquire_link
>     2007-04-11 09:03:46 [9121] [7] DEBUG:   command_id: 21 = 0x00000015
>     2007-04-11 09:03:46 [9121] [7] DEBUG:   command_status: 0 = 0x00000000
>     2007-04-11 09:03:46 [9121] [7] DEBUG:   sequence_number: 40108 = 
> 0x00009cac
>     2007-04-11 09:03:46 [9121] [7] DEBUG: SMPP PDU dump ends.
>     2007-04-11 09:03:46 [9121] [7] DEBUG:
>     SMPP[SMPP:********:5000/5000:****:*****]: Got PDU:
>     2007-04-11 09:03:46 [9121] [7] DEBUG: SMPP PDU 0x86c40b0 dump:
>     2007-04-11 09:03:46 [9121] [7] DEBUG:   type_name: enquire_link_resp
>     2007-04-11 09:03:46 [9121] [7] DEBUG:   command_id: 2147483669 = 
> 0x80000015
>     2007-04-11 09:03:46 [9121] [7] DEBUG:   command_status: 0 = 0x00000000
>     2007-04-11 09:03:46 [9121] [7] DEBUG:   sequence_number: 40108 = 
> 0x00009cac
>     2007-04-11 09:03:46 [9121] [7] DEBUG: SMPP PDU dump ends.
>      
>     3.    SMSs are successfully received but not sent. Restarting kannel 
> solves
>     the problem.
>      
>     This seems to suggest that the Tx TCP connection in kannel has become 
> stale
>     and doesn't reconnect. But then why do the enquire-links work? I assume 
> the
>     tx SMSs and the enquire-links go out on the same connection?
>      
>     If anyone has seen this before it would be very helpful. We're a bit 
> worried
>     because we have to restart kannel almost daily.
>      
>     Thanks,
>     Cyrus
>      
>     
>      
>     
>     Best Regards,
>     
>      
>     
>     Cyrus Patel
>     
>     Senior Software Engineer
>     
>     TEL: +612 9499 9848
>     
>     MOB: +61 413 685 795 
>     FAX: +612 9499 9845 
>     [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
>     
>     
>     Seeker Wireless is a registered trademark of Seeker Wireless Pty. Ltd., 
> ABN
>     95 106 550 805. This electronic mail includes information from Seeker
>     Wireless Pty Ltd which may be privileged or confidential. This information
>     is for the use of the individual(s) or entity named in the greeting above.
>     If you are not the intended recipient please be aware that any use of this
>     information is prohibited. If you have received this electronic mail in
>     error, please notify the sender (above) by return email.
>     
>      
>     
>     
> 
> 
> 

Reply via email to