[lobo]

hoffe es kann mir hier im Forum geholfen werden. Habe 3cx Free installiert. 3cx ist auf windows xp pro SP2 installiert u. ueber Linksys DDWRT ans Internet angeschlossen.

Habe zuerst Skype gateway installiert und funktioniert ohne Probleme. Anschliessend Sipgate voip Account integriert und es ergibt sich folgendes Problem. Schnittstelle angemeldet und zeigt gruen. Anruf bei Sipgate Echotest ok mit Ton. Anrufen einer Nummer, es klingelt das Telefon aber kein Ton in beide Richtungen. Der Fehler zeigt sich sowohl beim GXP2020 als auch beim 3cx Softphone identisch. Wenn ich aber Sipgate ohne 3cx ueber WLAN mit meinem Handy anrufe habe ich Ton. Anbei angehaengtes Protokoll einmal mit der Echotestrufnummer 10000 mit Ton, und der nicht funktionierenden Nummer 50000 Anrufbeantworter Sipgate ohne Ton. Wie komme ich nun weiter? Bin um jede Hilfe dankbar. Das Checker Protokoll ist angehaengt. waere es moeglich das 3cx nur ueber Sipgate trunk laueft?


bei diesem Protokoll mit abhoeren des Anrufbeantworter Anwahl 50000 kann ich kein Ton hoeren.

10:09:56.812 [MS105000] C:17.2: No RTP packets were received:remoteAddr=217.10.77.23:44116,extAddr=0.0.0.0:0,localAddr=192.168.5.112:7066
10:09:56.000 [CM503008]: Call(17): Call is terminated
10:09:52.828 Session 1029 of leg C:17.1 is confirmed
10:09:52.734 [CM503007]: Call(17): Device joined: sip:9573151@sipgate.de:5060
10:09:52.718 [CM503007]: Call(17): Device joined: sip:100@192.168.5.102:5060;transport=udp;user=phone
10:09:52.703 [MS210003] C:17.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.5.112:7064(7065)
10:09:52.703 [MS210001] C:17.2:Answer received. RTP connection[unsecure]: 217.10.77.23:44116(44117)
10:09:52.687 Remote SDP is set for legC:17.2
10:09:52.687 [CM505003]: Provider:[Sipgate Wolfgang] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:9573151@192.168.5.112:5060]
10:09:52.687 [CM503002]: Call(17): Alerting sip:9573151@sipgate.de:5060
10:09:51.968 [CM503025]: Call(17): Calling VoIPline:50000@(Ln.10001@Sipgate Wolfgang)@[Dev:sip:9573151@sipgate.de:5060]
10:09:51.953 [MS210002] C:17.2:Offer provided. Connection(transcoding mode): 192.168.5.112:7066(7067)
10:09:51.937 [CM503004]: Call(17): Route 1: VoIPline:50000@(Ln.10001@Sipgate Wolfgang)@[Dev:sip:9573151@sipgate.de:5060]
10:09:51.921 [CM503010]: Making route(s) to <sip:250000@192.168.5.112:5060;user=phone>
10:09:51.921 [MS210000] C:17.1:Offer received. RTP connection: 192.168.5.102:5010(5011)
10:09:51.921 Remote SDP is set for legC:17.1
10:09:51.921 [CM505001]: Ext.100: Device info: Device Identified: [Man: Grandstream;Mod: GXP Series;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Grandstream GXP2020 1.2.5.2] PBX contact: [sip:100@192.168.5.112:5060]
10:09:51.906 [CM503001]: Call(17): Incoming call from Ext.100 to <sip:250000@192.168.5.112:5060;user=phone>
10:09:51.890 [CM500002]: Info on incoming INVITE:
INVITE sip:250000@192.168.5.112:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.5.102:5060;branch=z9hG4bKaa73633d62291c52
Max-Forwards: 70
Contact: <sip:100@192.168.5.102:5060;transport=udp;user=phone>
To: <sip:250000@192.168.5.112:5060;user=phone>
From: "Wolfgang Grandstream casalobo"<sip:100@192.168.5.112:5060;user=phone>;tag=6fb206b851561216
Call-ID: ebad2fa6f8731393@192.168.5.102
CSeq: 44201 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK, MESSAGE
Proxy-Authorization: Digest username="100",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:250000@192.168.5.112:5060;user=phone",nonce="414d535c0301be4f34:4879b520102287588603fa3fdfa063e0",response="8c98f132a9e5d403954b3630c786fb02"
Supported: replaces, timer, path
User-Agent: Grandstream GXP2020 1.2.5.2
Content-Length: 0
X-Grandstream-PBX: true
P-Early-Media: Supported


bei diesem Protokoll Echotest 10000 oder 10005 ist der Ton zu hoeren

10:09:48.234 [CM503008]: Call(16): Call is terminated
10:09:44.953 Session 1023 of leg C:16.1 is confirmed
10:09:44.890 [CM503007]: Call(16): Device joined: sip:9573151@sipgate.de:5060
10:09:44.875 [CM503007]: Call(16): Device joined: sip:100@192.168.5.102:5060;transport=udp;user=phone
10:09:44.875 [MS210003] C:16.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.5.112:7060(7061)
10:09:44.859 [MS210001] C:16.2:Answer received. RTP connection[unsecure]: 217.10.77.41:62154(62155)
10:09:44.859 Remote SDP is set for legC:16.2
10:09:44.859 [CM505003]: Provider:[Sipgate Wolfgang] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:9573151@192.168.5.112:5060]
10:09:44.859 [CM503002]: Call(16): Alerting sip:9573151@sipgate.de:5060
10:09:44.109 [CM503025]: Call(16): Calling VoIPline:10000@(Ln.10001@Sipgate Wolfgang)@[Dev:sip:9573151@sipgate.de:5060]
10:09:44.109 [MS210002] C:16.2:Offer provided. Connection(transcoding mode): 192.168.5.112:7062(7063)
10:09:44.046 [CM503004]: Call(16): Route 1: VoIPline:10000@(Ln.10001@Sipgate Wolfgang)@[Dev:sip:9573151@sipgate.de:5060]
10:09:44.031 [CM503010]: Making route(s) to <sip:210000@192.168.5.112:5060;user=phone>
10:09:44.015 [MS210000] C:16.1:Offer received. RTP connection: 192.168.5.102:5006(5007)
10:09:43.843 Remote SDP is set for legC:16.1
10:09:43.843 [CM505001]: Ext.100: Device info: Device Identified: [Man: Grandstream;Mod: GXP Series;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [Grandstream GXP2020 1.2.5.2] PBX contact: [sip:100@192.168.5.112:5060]
10:09:43.625 [CM503001]: Call(16): Incoming call from Ext.100 to <sip:210000@192.168.5.112:5060;user=phone>
10:09:43.000 [CM500002]: Info on incoming INVITE:
INVITE sip:210000@192.168.5.112:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.5.102:5060;branch=z9hG4bK0e704f7087a32a6d
Max-Forwards: 70
Contact: <sip:100@192.168.5.102:5060;transport=udp;user=phone>
To: <sip:210000@192.168.5.112:5060;user=phone>
From: "Wolfgang Grandstream casalobo"<sip:100@192.168.5.112:5060;user=phone>;tag=f4606f234513b729
Call-ID: 14ba85b05c6ebc17@192.168.5.102
CSeq: 55342 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK, MESSAGE
Proxy-Authorization: Digest username="100",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:210000@192.168.5.112:5060;user=phone",nonce="414d535c0301be4683:ff09725587c7efcf87d7c3999ff30057",response="bb3408c5319c133030899ead2c13a98c"
Supported: replaces, timer, path
User-Agent: Grandstream GXP2020 1.2.5.2
Content-Length: 0
X-Grandstream-PBX: true
P-Early-Media: Supported




3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

<11:26:00>: Phase 1, checking servers connection, please wait...
<11:26:01>: Stun Checker service is reachable. Phase 1 check passed.
<11:26:01>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
<11:26:02>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 63719::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

<11:26:02>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
<11:26:02>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 63719::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

<11:26:02>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
<11:26:03>: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 58642::5090. Phase 3 check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

<11:26:03>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
<11:26:20>: UDP RTP Port 9000. Response received WITH TRANSLATION 58643::9000. Phase 4-01 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9001. Response received WITH TRANSLATION 58644::9001. Phase 4-02 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9002. Response received WITH TRANSLATION 58645::9002. Phase 4-03 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9003. Response received WITH TRANSLATION 58646::9003. Phase 4-04 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9004. Response received WITH TRANSLATION 58647::9004. Phase 4-05 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9005. Response received WITH TRANSLATION 58648::9005. Phase 4-06 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9006. Response received WITH TRANSLATION 58649::9006. Phase 4-07 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9007. Response received WITH TRANSLATION 58650::9007. Phase 4-08 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9008. Response received WITH TRANSLATION 58651::9008. Phase 4-09 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9009. Response received WITH TRANSLATION 58652::9009. Phase 4-10 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9010. Response received WITH TRANSLATION 58653::9010. Phase 4-11 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9011. Response received WITH TRANSLATION 58654::9011. Phase 4-12 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9012. Response received WITH TRANSLATION 58655::9012. Phase 4-13 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9013. Response received WITH TRANSLATION 58656::9013. Phase 4-14 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9014. Response received WITH TRANSLATION 58657::9014. Phase 4-15 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9015. Response received WITH TRANSLATION 58658::9015. Phase 4-16 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9016. Response received WITH TRANSLATION 58659::9016. Phase 4-17 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9017. Response received WITH TRANSLATION 58660::9017. Phase 4-18 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9018. Response received WITH TRANSLATION 58661::9018. Phase 4-19 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9019. Response received WITH TRANSLATION 58662::9019. Phase 4-20 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9020. Response received WITH TRANSLATION 58663::9020. Phase 4-21 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9021. Response received WITH TRANSLATION 58664::9021. Phase 4-22 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9022. Response received WITH TRANSLATION 58665::9022. Phase 4-23 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9023. Response received WITH TRANSLATION 58666::9023. Phase 4-24 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9024. Response received WITH TRANSLATION 58667::9024. Phase 4-25 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9025. Response received WITH TRANSLATION 58668::9025. Phase 4-26 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9026. Response received WITH TRANSLATION 58669::9026. Phase 4-27 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9027. Response received WITH TRANSLATION 58670::9027. Phase 4-28 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9028. Response received WITH TRANSLATION 58671::9028. Phase 4-29 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9029. Response received WITH TRANSLATION 58672::9029. Phase 4-30 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9030. Response received WITH TRANSLATION 58673::9030. Phase 4-31 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9031. Response received WITH TRANSLATION 58674::9031. Phase 4-32 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9032. Response received WITH TRANSLATION 58675::9032. Phase 4-33 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:20>: UDP RTP Port 9033. Response received WITH TRANSLATION 58676::9033. Phase 4-34 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9034. Response received WITH TRANSLATION 58677::9034. Phase 4-35 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9035. Response received WITH TRANSLATION 58678::9035. Phase 4-36 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9036. Response received WITH TRANSLATION 58679::9036. Phase 4-37 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9037. Response received WITH TRANSLATION 58680::9037. Phase 4-38 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9038. Response received WITH TRANSLATION 58681::9038. Phase 4-39 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9039. Response received WITH TRANSLATION 58703::9039. Phase 4-40 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9040. Response received WITH TRANSLATION 58704::9040. Phase 4-41 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9041. Response received WITH TRANSLATION 58705::9041. Phase 4-42 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9042. Response received WITH TRANSLATION 58706::9042. Phase 4-43 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9043. Response received WITH TRANSLATION 58707::9043. Phase 4-44 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9044. Response received WITH TRANSLATION 58708::9044. Phase 4-45 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9045. Response received WITH TRANSLATION 58709::9045. Phase 4-46 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9046. Response received WITH TRANSLATION 58710::9046. Phase 4-47 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9047. Response received WITH TRANSLATION 58711::9047. Phase 4-48 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9048. Response received WITH TRANSLATION 58712::9048. Phase 4-49 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:26:21>: UDP RTP Port 9049. Response received WITH TRANSLATION 58713::9049. Phase 4-50 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

[lobo]

keiner eine Idee wie ich weiter vorgehen koennte

[groundhog]

Ich habe die Konfiguration noch nicht getestet und kann keine fundierte Aussage treffen, aber das hört sich zunächst an wie ein klassischer Routing-Fehler.
Andererseits schließt Du das aus, in dem Du sagst das ein anderer Testanruf einwandfrei funktionieren würde.

Es werden offensichtlich keine RTP-Pakete geroutet, warum auch immer. Zunächst würde ich die Settings bei allen Beteiligten prüfen und dann auch das Routing.

Wenn da nichts zu finden ist, den Anruf einmal mit Wireshark mitschneiden und das Protokoll ggf. hier zugänglich machen-

[StefanW]

der firewall checker sagt mir schon das NAT nicht richtig ist, oder SIP ALG an ist, was ist es für eine Firewall?

[lobo]

folgendes habe ich noch getestet. Anlegen eines GIZMO Sipphone Acount. Es verhaelt sich exact gleich wie bei Sipgate.
Ansage von Gizmo mit Ton. Jedoch habe ich kein Ton in beiden Richtungen bei Anrufen.
Wenn ich ueber WLAN direkt ,ohne 3cx hinaustelefoniere funktioniert es. Anrufe von aussen kann ich aber ebenfalls
auch ohne 3cx nicht!!!!! empfangen, es klingelt dann nichtmal.[b]

[groundhog]

Welcher Router ist im Einsatz?

[groundhog]

....und auf welchem System ist 3CX installiert. Dort am besten mal die Firewall und den Virenscanner ausschalten und einen Anruf starten, damit klar ist das es nicht an der Rechnerumgebung liegt.

[lobo]

der firewall checker sagt mir schon das NAT nicht richtig ist, oder SIP ALG an ist, was ist es für eine Firewall?

der DDWRT hat kein SIP ALG Der SPI firewall WRT54 DDWRT voip version eingeschaltet. Zur Installation: liegt hinter dem Router
DDWRT ein Access point DWL 2100. Ueber diesen erhalte ich mein Internet Signal ueber ein externes WLAN Netz .

[lobo]

Welcher Router ist im Einsatz?

Linksys WRT54 Firmware: DD-WRT v24-sp1 (07/27/08) voipDD

[lobo]

....und auf welchem System ist 3CX installiert. Dort am besten mal die Firewall und den Virenscanner ausschalten und einen Anruf starten, damit klar ist das es nicht an der Rechnerumgebung liegt.

windows xp pro sp2 2002 version 5.1.2600 auf 3cx free v9 installiert . der Firewall auf windows ist generell ausgeschaltet.

[StefanW]

und die ports 5060 udp/tcp
9000-9049 udp
sind im nat gesetzt?

denn anch dem Firewall checker sieht es nicht gut aus...

[lobo]

und die ports 5060 udp/tcp
9000-9049 udp
sind im nat gesetzt?

denn anch dem Firewall checker sieht es nicht gut aus...

Port

DDWRT.PORT.png (72.83 KiB) Viewed 831 times

[StefanW]

http://www.dd-wrt.com/phpBB2/viewtopic.php?p=503275

da ist sip alg drin...

[lobo]

http://www.dd-wrt.com/phpBB2/viewtopic.php?p=503275

da ist sip alg drin...

der Milkfish ist ja SIP ALG das wusste ich nicht, der ist aber ausgeschaltet.

[groundhog]

Deshalb klappt auch dieses §$%!"§-Skype und kein SIP.

Dann kann der Testanruf aber auch nicht sauber gelaufen sein.