OC31 dreht jetzt völlig durch..

Hallo,

mittlerweile meldet sich die Anlage nur noch bei 1 von 3 Providern an (ohne Fehlermeldung), zwischendurch gab es dann auch beim Siplog Zeichensalat YYYYY und ähnliches, sieht nicht gut aus.

2006-06-20 22:04:10 STUN: NAT Type for account #2(tel.t-online.de): Full cone NAT
2006-06-20 22:04:15 STUN: NAT Type for account #3(sip.web.de): Full cone NAT
2006-06-20 22:04:20 STUN: NAT Type for account #4(sipgate.de): Full cone NAT
2006-06-20 22:04:30 Registering with SIP server account #3(sip.web.de)
2006-06-20 22:04:30 Successfully registered with SIP server account #3(sip.web.de) for 3603 seconds
2006-06-20 22:06:15 Registering with SIP server account #3(sip.web.de)
2006-06-20 22: hü@th SIP server account #3(sip.web.de) for 3600 seconds (tolle Zeichen im Log)
2006-06-20 22:06:30 Registering with SIP server account #3(sip.web.de)
2006-06-20 22:06:30 Successfully registered with SIP server account #3(sip.web.de) for 3603 seconds
.....

2006-06-20 22:04:10 STUN: NAT Type for account #2(tel.t-online.de): Full cone NAT
2006-06-20 22:04:15 STUN: NAT Type for account #3(sip.web.de): Full cone NAT
2006-06-20 22:04:20 STUN: NAT Type for account #4(sipgate.de): Full cone NAT
2006-06-20 22:04:30 Registering with SIP server account #3(sip.web.de)
2006-06-20 22:04:30 Successfully registered with SIP server account #3(sip.web.de) for 3603 seconds
2006-06-20 22:06:15 Registering with SIP server account #3(sip.web.de)
2006-06-20 22:¬'@§@oth SIP server account #3(sip.web.de) for 3600 seconds
2006-06-20 22:06:30 Registering with SIP server account #3(sip.web.de)
2006-06-20 22:06:30 Successfully registered with SIP server account #3(sip.web.de) for 3603 seconds
2006-06-20 22:12:29 Registering with SIP server account #3(sip.web.de)
2006-06-20 22:12:30 Successfully registered with SIP server account #3(sip.web.de) for 3600 seconds
2006-06-20 22:12:44 Registering with SIP server account #3(sip.web.de)
2¬'@§@oregistered with SIP server account #3(sip.web.de) for 3603 seconds

mehr gibts dann nicht mehr.

Das kann nicht wirklich an der Hitze liegen.
Ich würde die FW dann doch noch mal auf den Prüfstand bringen.


Und obwohl ich gar nicht telefoniere, diese sinnlosen Meldung spuckt die OC 31 einfach mal so aus und zwar endlos:

2006-06-20 22:10:43 RTP session 10: Packets: 0 Lost: 1075379304 Overflow: 27 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:10:43 RTP session 11: Packets: 0 Lost: 1075379304 Overflow: 27 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:10:53 RTP session 8: Packets: 1074931416 Lost: 111 Overflow: 31 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:10:53 RTP session 10: Packets: 1074931416 Lost: 111 Overflow: 31 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:10:53 RTP session 11: Packets: 1074931416 Lost: 111 Overflow: 31 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:10:58 RTP session 8: Packets: 0 Lost: 1075379304 Overflow: 27 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:10:58 RTP session 10: Packets: 0 Lost: 1075379304 Overflow: 27 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:10:58 RTP session 11: Packets: 0 Lost: 1075379304 Overflow: 27 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms


2006-06-20 22:13:13 RTP session 8: Packets: 0 Lost: 1075379304 Overflow: 27 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:13:13 RTP session 10: Packets: 0 Lost: 1075379304 Overflow: 27 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:13:13 RTP session 11: Packets: 0 Lost: 1075379304 Overflow: 27 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:13:13 RTP session 12: Packets: 0 Lost: 1075379304 Overflow: 27 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:13:18 RTP session 8: Packets: 1074931628 Lost: 111 Overflow: 31 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:13:18 RTP session 10: Packets: 1074931628 Lost: 111 Overflow: 31 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:13:18 RTP session 11: Packets: 1074931628 Lost: 111 Overflow: 31 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms
2006-06-20 22:13:18 RTP session 12: Packets: 1074931628 Lost: 111 Overflow: 31 Early: 0 Late: 0 Delay: 0 ms Last Gap: 0 ms


Das sieht schon merkwürdig aus, Software ist tot, würde ich sagen.

markesmith

Nachtrag...

Nach dem Flaschen mit der Version 2.55 ist wieder alles im Lot, also, Downgrade ist angesagt.

mark e smith