Asterisk@home 2.4 legt nach 30 Sekunden auf!

deathmaster99

Neuer User
Mitglied seit
13 Feb 2006
Beiträge
2
Punkte für Reaktionen
0
Punkte
0
Hallo,

erstmal danke an Leute die sich mit diesem Thema beschäftigen und uns "stupide
User" supporten. ;)

Ich habe folgenden Netzaufbau.

FritzBox 7050 mit eingerichteter UDP Portweiterleitung (5060-5080,10000-20000)
IP: 192.168.6.200
SM:255.255.255.0

Asterisk Server
IP: 192.168.6.199
SM:255.255.255.0


Ich habe beim Asterisk@Home 2.4 Server alles über das AMP eingerichtet.
Sipgate Account, auf welchen auch der Asterisk PBX in der Maske erkannt wird.(Ich denke das heißt das dann die Login Sache geklärt wär)

Ich habe eine Extension eingerichtet ID"123456".
Ein Queue/Schleife & halt den SIPgate Trunk (der sich wohl einzuloggen scheint //siehe oben//)

Allerdings ist die Extension nur am Asterisk eingerichtet, denn ich habe noch kein VoIP Phone oder Softphone eingerichtet.

Wenn ich nun auf der Sipgate Nummer anrufe kommt für ungefähr 30 sekunden nichts und dann legt er auf.

Habe hier mal eine Log-Datei während des Anrufs kopiert.
siehe unten

Log:
'/etc/asterisk/enum.conf': Found
May 18 11:53:54 VERBOSE[2673] logger.c: Asterisk Ready.
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Challenge'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Login'
May 18 11:53:58 VERBOSE[2757] logger.c: Asterisk Ready.
== Parsing '/etc/asterisk/manager.conf': May 18 11:53:58 VERBOSE[2757] logger.c: Asterisk Ready.
== Parsing '/etc/asterisk/manager.conf': Found
May 18 11:53:58 VERBOSE[2757] logger.c: == Parsing '/etc/asterisk/manager_custom.conf': May 18 11:53:58 VERBOSE[2757] logger.c: == Parsing '/etc/asterisk/manager_custom.conf': Found
May 18 11:53:58 WARNING[2757] config.c: Unknown directive 'permit=192.168.1.0/255.255.255.0' at line 18 of manager_custom.conf
May 18 11:53:58 DEBUG[2757] acl.c: 0.0.0.0/0.0.0.0/0.0.0.0 appended to acl for peer
May 18 11:53:58 DEBUG[2757] acl.c: 127.0.0.1/255.255.255.0/255.255.255.0 appended to acl for peer
May 18 11:53:58 DEBUG[2757] acl.c: ##### Testing 127.0.0.1 with 0.0.0.0
May 18 11:53:58 DEBUG[2757] acl.c: ##### Testing 127.0.0.1 with 127.0.0.0
May 18 11:53:58 VERBOSE[2757] logger.c: == Manager 'admin' logged on from 127.0.0.1
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] db.c: Unable to find key '1' in family 'cfb'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] db.c: Unable to find key 'SIP/123456' in family 'cfb'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] db.c: Unable to find key 'SIP/Sipgate' in family 'cfb'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] db.c: Unable to find key '1' in family 'dnd'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] db.c: Unable to find key 'SIP/123456' in family 'dnd'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] db.c: Unable to find key 'SIP/Sipgate' in family 'dnd'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'QueueStatus'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Status'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'ZapShowChannels'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'MailboxStatus'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:53:58 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:54:00 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:54:00 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:54:24 DEBUG[2710] chan_sip.c: Auto destroying call '[email protected]'
May 18 11:55:37 DEBUG[2710] chan_sip.c: Scheduled a registration timeout for sipgate.de id #7
May 18 11:55:38 DEBUG[2710] chan_sip.c: Stopping retransmission on '[email protected]' of Request 104: Match Found
May 18 11:55:38 DEBUG[2710] chan_sip.c: Registration successful
May 18 11:55:38 DEBUG[2710] chan_sip.c: Cancelling timeout 7
May 18 11:56:00 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:56:00 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:56:10 DEBUG[2710] chan_sip.c: Auto destroying call '[email protected]'
May 18 11:57:23 DEBUG[2710] chan_sip.c: Scheduled a registration timeout for sipgate.de id #11
May 18 11:57:23 DEBUG[2710] chan_sip.c: Stopping retransmission on '[email protected]' of Request 105: Match Found
May 18 11:57:23 DEBUG[2710] chan_sip.c: Registration successful
May 18 11:57:23 DEBUG[2710] chan_sip.c: Cancelling timeout 11
May 18 11:57:30 VERBOSE[3084] logger.c: -- Starting Skinny session from 192.168.6.4
May 18 11:57:30 WARNING[3084] chan_skinny.c: Skinny Client sent less data than expected.
May 18 11:57:30 NOTICE[3084] chan_skinny.c: Skinny Session returned: Success
May 18 11:57:31 VERBOSE[3085] logger.c: -- Starting Skinny session from 192.168.6.4
May 18 11:57:31 WARNING[3085] chan_skinny.c: Skinny Client sent less data than expected.
May 18 11:57:31 NOTICE[3085] chan_skinny.c: Skinny Session returned: Success
May 18 11:57:55 DEBUG[2710] chan_sip.c: Auto destroying call '[email protected]'
May 18 11:58:00 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:58:00 DEBUG[2757] manager.c: Manager received command 'Command'
May 18 11:59:08 DEBUG[2710] chan_sip.c: Scheduled a registration timeout for sipgate.de id #15
May 18 11:59:08 DEBUG[2710] chan_sip.c: Stopping retransmission on '[email protected]' of Request 106: Match Found
May 18 11:59:08 DEBUG[2710] chan_sip.c: Stopping retransmission on '[email protected]' of Request 107: Match Found
May 18 11:59:08 DEBUG[2710] chan_sip.c: Registration successful
May 18 11:59:08 DEBUG[2710] chan_sip.c: Cancelling timeout 15
May 18 11:59:13 DEBUG[2710] chan_sip.c: Setting NAT on RTP to 524288
May 18 11:59:13 DEBUG[2710] chan_sip.c: Stopping retransmission on '[email protected]' of Response 102: Match Found
May 18 11:59:13 DEBUG[2710] chan_sip.c: Setting NAT on RTP to 524288
May 18 11:59:13 DEBUG[2710] chan_sip.c: Stopping retransmission on '[email protected]' of Response 103: Match Found
May 18 11:59:13 DEBUG[2710] chan_sip.c: Setting NAT on RTP to 524288
May 18 11:59:13 DEBUG[2710] chan_sip.c: Stopping retransmission on '[email protected]' of Response 104: Match Found
May 18 11:59:28 DEBUG[2710] chan_sip.c: Auto destroying call '[email protected]'
May 18 11:59:40 DEBUG[2710] chan_sip.c: Auto destroying call '[email protected]'
May 18 11:59:40 DEBUG[2710] chan_sip.c: Auto destroying call '[email protected]'


ENDE

Ich entnehme aus diesen Text das irgendwo vieleicht ein NAT Problem vorliegt, weil " Auto destroying call " oben steht. D.H er reagiert ja schon.

Ich hoffe auf eure Hilfe und bin euch jetzt schon dankbar...

THX der deathmaster (PS. wer Hilfe in Sachen DBox2,CAMD,etc benötigt, einfach bei mir melden)
 
Zuletzt bearbeitet:
Hi deathmaster99,

es kann ein NAT-Problem sein, hast Du eine Firewall laufen?
Überprüf mal mit iptables -v -n -L, die RTP-Ports in
/etc/asterisk/rtp.conf müssen offen sein, die sip-ports ebenfalls.
Am besten Firewall kurz runter, dann testen.


Dann log Dich mal auf die CLI ein mit asterisk -vvvvvvvr
dann zeig mal:
sip show peers
sip show registry

Bei Sipgate gab es bei mir Schwierigkeiten als ich einmal über
Windows mit Stun reinkahm, dann war mich Linux nichts mehr
zu machen.

Gruß
britzelfix
 
Kostenlos!

Neueste Beiträge

Statistik des Forums

Themen
248,872
Beiträge
2,303,452
Mitglieder
378,532
Neuestes Mitglied
Nik320