Asterisk 1.6.2.2 auf FB 7270 einige Fehler(chen) bereinigen

[dariuszmarek]

Hallo zusammen, nachdem ich Asterisk-Binary und Module erfolgreich auf einer spblinux-Installation ersetzt habe, bekomme ich in der Konsole ein paar Fehlermeldungen.

Die Gespräche an für sich und alles funktioniert so weit ganz gut.

Nun die Fehler

Connected to Asterisk 1.6.2.20 currently running on fritz (pid = 14687)                                               
[Mar  8 23:57:37] ERROR[14687]: chan_unistim.c:5310 reload_config: Unable to load config unistim.conf
[Mar  8 23:57:37] WARNING[14687]: chan_mgcp.c:4228 reload_config: Failed to bind to 0.0.0.0:2727: Address already in use
[Mar  8 23:57:38] ERROR[14687]: chan_dongle.c:1667 public_state_init: Errors reading config file dongle.conf, Not loading module
[Mar  8 23:57:38] WARNING[14687]: cdr_sqlite3_custom.c:163 load_config: Failed to load configuration file. Module not activated.
[Mar  8 23:57:38] WARNING[14687]: app_minivm.c:2620 load_config: Failed to load configuration file. Module activated with default settings.
[Mar  8 23:57:38] WARNING[14687]: app_followme.c:314 reload_followme: No follow me config file (followme.conf), so no follow me
[Mar  8 23:57:38] ERROR[14687]: app_amd.c:426 load_config: Configuration file amd.conf missing.
SIP channel loading...
[Mar  8 23:57:38] ERROR[14687]: tcptls.c:478 ast_tcptls_server_start: Unable to bind SIP TCP server to 0.0.0.0:5062: Address already in use
[Mar  8 23:57:38] ERROR[14687]: chan_sip.c:25889 reload_config: SIP TCP Server start failed. Not listening on TCP socket.
[Mar  8 23:57:38] ERROR[14687]: pbx_dundi.c:4855 load_module: Unable to bind to 0.0.0.0 port 4520: Address already in use
[Mar  8 23:57:38] ERROR[14687]: ael.y:840 ael_yyerror: ==== File: (null), Line 1, Cols: 1-1: Error: syntax error, unexpected $end, expecting 'context'
[Mar  8 23:57:38] ERROR[14687]: pbx_ael.c:196 pbx_load_module: Sorry, but 1 syntax errors and 0 semantic errors were detected. It doesn't make sense to compile.
[Mar  9 00:27:48] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:27:49] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:28:02] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:28:02] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:28:09] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:28:10] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:28:23] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:28:23] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:35:02] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:35:25] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 00:35:34] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 05:45:02] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 05:45:02] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <622>
[Mar  9 06:00:01] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>
[Mar  9 06:00:01] WARNING[14716]: chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <622>

Lässt sich das was tun?

Danke!

 

[waldoo]

ja klar kannst du was dagegen tun.
z.B.:

chan_dongle.c:1667 public_state_init: Errors reading config file dongle.conf

=> Da fehlt einfach das Konfigurations file.
Entweder das Modul löschen (da Du es eh nicht brauchst) oder dongle.conf erstellen (Könnte auch leer sein)

chan_sip.c:13288 check_auth: username mismatch, have <702>, digest has <620>

=> sip.conf überarbeiten
Asterisk 1.6 ist ein wenig anders wie Asterisk 1.4 (von der kommt wahrscheinlich Deine aktuelle Konfiguration)