HILFE: *1.4.10 INSTABIL "Asked to transmit frame type" & "RTCP SR transmission error"

papaya74

Neuer User
Mitglied seit
5 Jan 2005
Beiträge
24
Punkte für Reaktionen
0
Punkte
0
Hallo zusammen,

nachdem ich nun schon alles abgesucht habe, möchte ich hier gerne die Intelligenz befragen ;)

1. Umstieg von * 1.2. auf 1.4.10
  • Wir haben mit der nachfolgenden Konfiguration seit Jahren stabil einen * unter Etch betrieben
  • Dabei wird von ISDN <--> * <--> Snom geroutet
  • Das ganze macht eine Sirrix.PCI4S0
  • Zum Einsatz kommen ca. 35 Snoms u.a. 190 / 320 / 360 / 370
Der neue Server läuft unter "Ubuntu 7.10 Server" mit default Asterisk 1.4.10 und auch einer Sirrix.PCI4S0

2. Nach dem wir einige Syntax-Fehler eleminiert hatten, lief erstmal alles gut, bis auf sich wiederholenden Fehler im syslog:

Code:
asterisk[10806]: rc_avpair_new: unknown attribute 1490026597

3. Gestern kam dann der erste komplette * Absturz mitten in Gesprächen:

Code:
Extension Changed 12 new state Idle for Notify User 29
[Mar 18 17:07:17] NOTICE[12490]: chan_sip.c:14736 handle_request_subscribe: Got SUBSCRIBE for extension 001702477821@default from 192.168.0.227, but there is no hint for that extension.
[Mar 18 17:07:17] NOTICE[12490]: chan_sip.c:14736 handle_request_subscribe: Got SUBSCRIBE for extension XXXX_Nummer_geändert@default from 192.168.0.227, but there is no hint for that extension.
    -- Started music on hold, class 'default', on channel 'Srx/gOut1-0x8432700'
   
Extension Changed 11 new state Hold for Notify User 26
 Extension Changed 11 new state Hold for Notify User 20
 Extension Changed 11 new state Hold for Notify User 32
 Extension Changed 11 new state Hold for Notify User 29
    -- Executing [27@default:1] Dial("SIP/11-0844f288", "SIP/27|45|wW") in new stack
    -- Called 27
 Extension Changed 27 new state Ringing for Notify User 21
 Extension Changed 27 new state Ringing for Notify User 11
 Extension Changed 27 new state Ringing for Notify User 24
 Extension Changed 27 new state Ringing for Notify User 26
 Extension Changed 27 new state Ringing for Notify User 32
    -- SIP/27-084409f8 is ringing
    -- SIP/27-084409f8 is ringing
    -- SIP/27-084409f8 is ringing
    -- SIP/27-084409f8 is ringing
    -- SIP/27-084409f8 answered SIP/11-0844f288
 Extension Changed 27 new state InUse for Notify User 21
    -- Packet2Packet bridging SIP/11-0844f288 and SIP/27-084409f8
 Extension Changed 27 new state InUse for Notify User 11
 Extension Changed 27 new state InUse for Notify User 24
 Extension Changed 27 new state InUse for Notify User 26
 Extension Changed 27 new state InUse for Notify User 32
RTCP SR transmission error, rtcp halted
RTCP SR transmission error, rtcp halted
    -- Stopped music on hold on Srx/gOut1-0x8432700
[Mar 18 17:07:44] WARNING[20588]: chan_sip.c:3661 sip_write: Can't send 138711660 type frames with SIP write
voipy-01*CLI> 
Disconnected from Asterisk server

4. Wir haben dann das musiconhold komplett deaktiviert

5. HEUTE wieder Ausfälle mit

Code:
[Mar 19 10:20:09] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:09] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:09] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)
[Mar 19 10:20:10] WARNING[29788] chan_sip.c: Asked to transmit frame type 64, while native formats is 0x4 (ulaw)(4) read/write = 0x4 (ulaw)(4)/0x4 (ulaw)(4)

6. Ich vermute den Fehler im SIP, deshalb hier mal die conf:

Code:
[general]
language=de
port = 5060
bindaddr = 0.0.0.0
Localnet = 192.168.0.0/255.255.0.0
srvlookup = yes
maxexpirey = 1200
defaultexpirey = 20

canreinvite=no
tos=0x18
insecure=very
nat=yes
qualify=yes

fromdomain=192.168.0.21
context=default

limitonpeers=yes
allowsubscribe=yes
notifyringing=yes
notifyhold=yes
useclientcode=yes

[11]
subscribecontext=default
type=friend
username=11
secret=
host=dynamic
callerid=11
disallow=all
allow=ulaw
dtmfmode=rfc2833
;notifyringing=yes
;useclientcode=yes
mailbox=11
vmexten=8011
callgroup=1
pickupgroup=1
call-limit=99

7. rtp.conf steht auf default values...

Hat jemand eine Idee, wo das Problem liegen könnte ?
Vielen Dank & Gruss,

Harry Jung
 
Gab es bei dem Problem bereits eine Lösung??
 
die Antwort = Jein...

Wir haben festgestellt, dass * 1.4.10 unter Ubuntu-Server buggy ist, und / oder sich mit der Sirrix-Karte und den Treibern irgendwie nicht verstanden hat.

Die Version(en) ist/sind einfach nicht stable !

Lösung: Verwende "Debian Etch/Lenny" und die im repository enthaltene Asterisk Version, sowie die aktuellen Treiber zur Sirrix-Karte , falls Du diese einsetzt.

Debian = stable = stable = stable ;)
 
Holen Sie sich 3CX - völlig kostenlos!
Verbinden Sie Ihr Team und Ihre Kunden Telefonie Livechat Videokonferenzen

Gehostet oder selbst-verwaltet. Für bis zu 10 Nutzer dauerhaft kostenlos. Keine Kreditkartendetails erforderlich. Ohne Risiko testen.

3CX
Für diese E-Mail-Adresse besteht bereits ein 3CX-Konto. Sie werden zum Kundenportal weitergeleitet, wo Sie sich anmelden oder Ihr Passwort zurücksetzen können, falls Sie dieses vergessen haben.