Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic Probleme mit Phoner (Read 4186 times)
Bravosix
YaBB Newbies
*
Offline


Phoner ist großartig!

Posts: 4
Joined: 02. Mar 2008
Probleme mit Phoner
02. Mar 2008 at 03:55
Print Post  
Also folgendes ich bin im mom im Auslandseinsatz im Kosovo...
Meine anderen Kameraden hier nutzen auch Sipgate nur haben die Xp drauf und somit telefonieren die alle mit Sipgate X lite dem vor konfiguriertem Prog von Sipgate....und es funzt ohne Probs

Ich nutze Vista Ultimate und muss also mit PhonerLite telefonieren laut Sipgate.

Mein Phoner ist genau wie bei Sipgate beschrieben konfiguriert. Es kommt aber keine Verbindung zustande. Ich kann mich auf der Sipgate Nummer vom Handy aus selber anrufen, es klingelt auch aber sobald ich das Gespräch annehme ist auf beiden Seiten nichts zu hören. Raustelefonieren funzt überhaupt nicht da bekomme ich immer die Meldung 408:Request Timeout.

Kann das an den Port bzw Netzwereinstellungen von Vista liegen ??

Hoffe Ihr könnt mir hierbei irgendwie helfen 

mfg Stefan
  
Back to top
 
IP Logged
 
Bravosix
YaBB Newbies
*
Offline


Phoner ist großartig!

Posts: 4
Joined: 02. Mar 2008
Re: Probleme mit Phoner
Reply #1 - 02. Mar 2008 at 03:57
Print Post  
03:44:08,865: Start of application PhonerLite
03:44:08,939: load configuration
03:44:09,254: load SIP settings
03:44:09,256: Loading profiles from configuration file: C:\Program Files\PhonerLite\sipper.ini
03:44:09,340: Loading profile "Wizard_sipgate.de" from configuration file: C:\Program Files\PhonerLite\sipper.ini
03:44:09,470: OpenDevice (sipper.dll)
03:44:09,471: LoadCAPI(sipper.dll)
03:44:09,545: Installed
03:44:09,547: Installed: 
03:44:09,549: Get Manufacturer: 53 49 50 50 45 52 
03:44:09,550: Get Version: 02 00 00 00 00 00 00 00 01 00 00 00 37 00 00 00 
03:44:09,553: SIPPER: 2.0 (1.55)
03:44:09,555: Register: 240 bytes blocksize
03:44:09,557: Register: 00 0C 00 00 02 00 00 00 07 00 00 00 F0 00 00 00 
03:44:09,599: Register returns: 01 00 00 00 
03:44:09,604: CAPI thread created: 0x0350
03:44:09,605: Get Profile: 01 00 08 00 19 00 00 00 03 00 00 00 03 00 00 00 01 00 00 00 1F 43 40 00 80 F0 12 00 58 F4 12 00 A0 01 23 01 01 00 1F 01 F0 01 8D 77 74 5A 40 76 50 03 00 00 94 F0 12 00 FC F0 12 00 A0 01 23 01 
03:44:09,673: Listen Request: 1A 00 01 00 05 80 02 00 01 00 00 00 FF 17 00 00 12 00 01 00 00 00 00 00 00 00 
03:44:09,675: Listen Request
03:44:09,678: Facility Request: 12 00 01 00 80 80 04 00 01 00 00 00 03 00 03 00 00 00 
03:44:09,687: Facility Request (Get Supplementary Services)
-------------------------------------------
03:44:09,620: R: DNS lookup for 'stun.sipgate.net'
start resolving...
-------------------------------------------
03:44:09,672: R: DNS lookup for 'stun.sipgate.net'
217.10.79.2
-------------------------------------------
03:44:09,674: R: DNS lookup for 'sipgate.de'
start resolving...
-------------------------------------------
03:44:10,541: R: DNS lookup for 'sipgate.de'
217.10.79.9
-------------------------------------------
03:44:10,567: T: 217.10.79.2:10000
STUN requesting...
-------------------------------------------
03:44:12,014: T: 217.10.79.2:10000
STUN
  public ip: 62.192.129.46:32783


-------------------------------------------
03:44:12,048: Listen Confirm: 0E 00 01 00 05 81 02 00 01 00 00 00 00 00 
03:44:12,056: Listen Confirm
-------------------------------------------
03:44:12,022: R: DNS lookup for 'sipgate.de'
start resolving SRV (UDP)...
-------------------------------------------
03:44:12,557: R: DNS lookup for 'sipgate.de'
217.10.79.9:5060
-------------------------------------------
03:44:12,571: Facility Confirm: 1A 00 01 00 80 81 04 00 01 00 00 00 00 00 03 00 09 00 00 06 00 00 3D 01 00 00 
03:44:12,574: Facility Confirm (Supplementary Services): Get Supported Services -> success
03:44:12,576: Facility Request: 16 00 01 00 80 80 05 00 01 00 00 00 03 00 07 01 00 04 3D 01 00 00 
03:44:12,578: Facility Request (Listen To Supplementary Services)
-------------------------------------------
03:44:12,557: T: 217.10.79.9:5060 (UDP)
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK00a6583570e6dc11a050001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=1158329019
To: <sip:7368103@sipgate.de>
Call-ID: 80E28E33-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 1 REGISTER
Contact: <sip:7368103@62.192.129.46:32783>
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
User-Agent: SIPPER for PhonerLite
Expires: 900
Event: registration
Content-Length: 0


-------------------------------------------
03:44:12,585: Facility Confirm: 16 00 01 00 80 81 05 00 01 00 00 00 00 00 03 00 05 01 00 02 00 00 
03:44:12,588: Facility Confirm (Supplementary Services): Listen -> success
-------------------------------------------
03:44:13,058: T: 217.10.79.9:5060 (UDP)
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK00a6583570e6dc11a050001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=1158329019
To: <sip:7368103@sipgate.de>
Call-ID: 80E28E33-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 1 REGISTER
Contact: <sip:7368103@62.192.129.46:32783>
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
User-Agent: SIPPER for PhonerLite
Expires: 900
Event: registration
Content-Length: 0


-------------------------------------------
03:44:13,133: R: 217.10.79.9:5060 (UDP)
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.31.250.4:32783;branch=z9hG4bK00a6583570e6dc11a050001de01299a3;rport=5060
From: "7368103" <sip:7368103@sipgate.de>;tag=1158329019
To: <sip:7368103@sipgate.de>;tag=fe1721141f05bd30d4b50c70da3ae228.f03b
Call-ID: 80E28E33-70E6-DC11-A050-001DE01299A3@172.31.250.4
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sipgate.de", nonce="47ca15ad19afe7944ea90b56b1a8e8cdc185a5b6"
Content-Length: 0


-------------------------------------------
03:44:13,133: T: 217.10.79.9:5060 (UDP)
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK803cf13570e6dc11a050001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=2830416673
To: <sip:7368103@sipgate.de>
Call-ID: 80E28E33-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 2 REGISTER
Contact: <sip:7368103@62.192.129.46:32783>
Authorization: Digest username="7368103", realm="sipgate.de", nonce="47ca15ad19afe7944ea90b56b1a8e8cdc185a5b6", uri="sip:sipgate.de", response="e3492298cd7dc6bc34b67e51b23b59bd", algorithm=MD5
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
User-Agent: SIPPER for PhonerLite
Expires: 900
Event: registration
Content-Length: 0


-------------------------------------------
03:44:13,618: R: 217.10.79.9:5060 (UDP)
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.31.250.4:32783;branch=z9hG4bK00a6583570e6dc11a050001de01299a3;rport=5060
From: "7368103" <sip:7368103@sipgate.de>;tag=1158329019
To: <sip:7368103@sipgate.de>;tag=fe1721141f05bd30d4b50c70da3ae228.f03b
Call-ID: 80E28E33-70E6-DC11-A050-001DE01299A3@172.31.250.4
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sipgate.de", nonce="47ca15ad19afe7944ea90b56b1a8e8cdc185a5b6"
Content-Length: 0


-------------------------------------------
03:44:13,634: T: 217.10.79.9:5060 (UDP)
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK803cf13570e6dc11a050001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=2830416673
To: <sip:7368103@sipgate.de>
Call-ID: 80E28E33-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 2 REGISTER
Contact: <sip:7368103@62.192.129.46:32783>
Authorization: Digest username="7368103", realm="sipgate.de", nonce="47ca15ad19afe7944ea90b56b1a8e8cdc185a5b6", uri="sip:sipgate.de", response="e3492298cd7dc6bc34b67e51b23b59bd", algorithm=MD5
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
User-Agent: SIPPER for PhonerLite
Expires: 900
Event: registration
Content-Length: 0


-------------------------------------------
03:44:13,728: R: 217.10.79.9:5060 (UDP)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.31.250.4:32783;branch=z9hG4bK803cf13570e6dc11a050001de01299a3;rport=5060
From: "7368103" <sip:7368103@sipgate.de>;tag=2830416673
To: <sip:7368103@sipgate.de>;tag=fe1721141f05bd30d4b50c70da3ae228.1947
Call-ID: 80E28E33-70E6-DC11-A050-001DE01299A3@172.31.250.4
CSeq: 2 REGISTER
Contact: <sip:7368103@172.31.250.4:32783>;expires=600;received="sip:172.31.250.4:5060"
Content-Length: 0


-------------------------------------------
03:44:14,208: R: 217.10.79.9:5060 (UDP)
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.31.250.4:32783;branch=z9hG4bK803cf13570e6dc11a050001de01299a3;rport=5060
From: "7368103" <sip:7368103@sipgate.de>;tag=2830416673
To: <sip:7368103@sipgate.de>;tag=fe1721141f05bd30d4b50c70da3ae228.1947
Call-ID: 80E28E33-70E6-DC11-A050-001DE01299A3@172.31.250.4
CSeq: 2 REGISTER
Contact: <sip:7368103@172.31.250.4:32783>;expires=599;received="sip:172.31.250.4:5060"
Content-Length: 0


-------------------------------------------
03:44:43,144: Connect Request: 31 00 01 00 02 80 06 00 01 00 00 00 01 00 06 80 31 30 30 30 30 09 00 80 37 33 36 38 31 30 33 00 00 09 01 00 01 00 00 00 00 00 00 00 00 02 91 81 00 
03:44:43,171: Connect Request: 7368103 to 10000
-------------------------------------------
03:44:43,172: R: DNS lookup for 'sipgate.de'
start resolving SRV (UDP)...
-------------------------------------------
03:44:43,173: R: DNS lookup for 'sipgate.de'
217.10.79.9:5060
-------------------------------------------
03:44:43,174: T: 217.10.79.2:10000
STUN requesting...
-------------------------------------------
03:44:44,777: T: 217.10.79.2:10000
STUN
  public ip: 62.192.129.46:32855


-------------------------------------------
03:44:46,613: Connect Confirm: 0E 00 01 00 02 81 06 00 01 01 00 00 00 00 
03:44:46,642: Connect Confirm
-------------------------------------------
03:44:46,613: T: 217.10.79.9:5060 (UDP)
INVITE sip:10000@sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK80dfd24770e6dc11a051001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=1246777423
To: <sip:10000@sipgate.de>
Call-ID: 80DFD247-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 3 INVITE
Contact: <sip:7368103@62.192.129.46:32783>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel, replaces
User-Agent: SIPPER for PhonerLite
Content-Length:   387

v=0
o=- 3071651590 0 IN IP4 62.192.129.46
s=SIPPER for PhonerLite
c=IN IP4 62.192.129.46
t=0 0
m=audio 32855 RTP/AVP 8 0 2 3 97 110 111 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:110 speex/8000
a=rtpmap:111 speex/16000
a=rtpmap:101 telephone-event/8000
a=rtcp:5063
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
03:44:47,114: T: 217.10.79.9:5060 (UDP)
INVITE sip:10000@sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK80dfd24770e6dc11a051001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=1246777423
To: <sip:10000@sipgate.de>
Call-ID: 80DFD247-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 3 INVITE
Contact: <sip:7368103@62.192.129.46:32783>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel, replaces
User-Agent: SIPPER for PhonerLite
Content-Length:   387

v=0
o=- 3071651590 0 IN IP4 62.192.129.46
s=SIPPER for PhonerLite
c=IN IP4 62.192.129.46
t=0 0
m=audio 32855 RTP/AVP 8 0 2 3 97 110 111 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:110 speex/8000
a=rtpmap:111 speex/16000
a=rtpmap:101 telephone-event/8000
a=rtcp:5063
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
03:44:48,115: T: 217.10.79.9:5060 (UDP)
INVITE sip:10000@sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK80dfd24770e6dc11a051001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=1246777423
To: <sip:10000@sipgate.de>
Call-ID: 80DFD247-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 3 INVITE
Contact: <sip:7368103@62.192.129.46:32783>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel, replaces
User-Agent: SIPPER for PhonerLite
Content-Length:   387

v=0
o=- 3071651590 0 IN IP4 62.192.129.46
s=SIPPER for PhonerLite
c=IN IP4 62.192.129.46
t=0 0
m=audio 32855 RTP/AVP 8 0 2 3 97 110 111 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:110 speex/8000
a=rtpmap:111 speex/16000
a=rtpmap:101 telephone-event/8000
a=rtcp:5063
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
03:44:50,116: T: 217.10.79.9:5060 (UDP)
INVITE sip:10000@sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK80dfd24770e6dc11a051001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=1246777423
To: <sip:10000@sipgate.de>
Call-ID: 80DFD247-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 3 INVITE
Contact: <sip:7368103@62.192.129.46:32783>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel, replaces
User-Agent: SIPPER for PhonerLite
Content-Length:   387

v=0
o=- 3071651590 0 IN IP4 62.192.129.46
s=SIPPER for PhonerLite
c=IN IP4 62.192.129.46
t=0 0
m=audio 32855 RTP/AVP 8 0 2 3 97 110 111 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:110 speex/8000
a=rtpmap:111 speex/16000
a=rtpmap:101 telephone-event/8000
a=rtcp:5063
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
03:44:54,117: T: 217.10.79.9:5060 (UDP)
INVITE sip:10000@sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK80dfd24770e6dc11a051001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=1246777423
To: <sip:10000@sipgate.de>
Call-ID: 80DFD247-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 3 INVITE
Contact: <sip:7368103@62.192.129.46:32783>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel, replaces
User-Agent: SIPPER for PhonerLite
Content-Length:   387

v=0
o=- 3071651590 0 IN IP4 62.192.129.46
s=SIPPER for PhonerLite
c=IN IP4 62.192.129.46
t=0 0
m=audio 32855 RTP/AVP 8 0 2 3 97 110 111 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:110 speex/8000
a=rtpmap:111 speex/16000
a=rtpmap:101 telephone-event/8000
a=rtcp:5063
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
03:45:02,118: T: 217.10.79.9:5060 (UDP)
INVITE sip:10000@sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK80dfd24770e6dc11a051001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=1246777423
To: <sip:10000@sipgate.de>
Call-ID: 80DFD247-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 3 INVITE
Contact: <sip:7368103@62.192.129.46:32783>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel, replaces
User-Agent: SIPPER for PhonerLite
Content-Length:   387

v=0
o=- 3071651590 0 IN IP4 62.192.129.46
s=SIPPER for PhonerLite
c=IN IP4 62.192.129.46
t=0 0
m=audio 32855 RTP/AVP 8 0 2 3 97 110 111 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:110 speex/8000
a=rtpmap:111 speex/16000
a=rtpmap:101 telephone-event/8000
a=rtcp:5063
a=fmtp:101 0-15
a=sendrecv

  
Back to top
 
IP Logged
 
Bravosix
YaBB Newbies
*
Offline


Phoner ist großartig!

Posts: 4
Joined: 02. Mar 2008
Re: Probleme mit Phoner
Reply #2 - 02. Mar 2008 at 04:01
Print Post  
03:45:18,119: T: 217.10.79.9:5060 (UDP)
INVITE sip:10000@sipgate.de SIP/2.0
Via: SIP/2.0/UDP 62.192.129.46:32783;branch=z9hG4bK80dfd24770e6dc11a051001de01299a3;rport
From: "7368103" <sip:7368103@sipgate.de>;tag=1246777423
To: <sip:10000@sipgate.de>
Call-ID: 80DFD247-70E6-DC11-A050-001DE01299A3@62.192.129.46
CSeq: 3 INVITE
Contact: <sip:7368103@62.192.129.46:32783>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel, replaces
User-Agent: SIPPER for PhonerLite
Content-Length:   387

v=0
o=- 3071651590 0 IN IP4 62.192.129.46
s=SIPPER for PhonerLite
c=IN IP4 62.192.129.46
t=0 0
m=audio 32855 RTP/AVP 8 0 2 3 97 110 111 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:110 speex/8000
a=rtpmap:111 speex/16000
a=rtpmap:101 telephone-event/8000
a=rtcp:5063
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
03:45:18,616: Disconnect Indication: 0E 00 01 00 04 82 48 00 01 01 00 00 92 38 
03:45:18,640: Disconnect Indication: 18:No user responding
03:45:18,665: Disconnect Response: 0C 00 01 00 04 83 48 00 01 01 00 00 
03:45:18,676: Disconnect Response


Dachte ich post mal das Dbug Log vll kann ja jemand was damit anfangen....
  
Back to top
 
IP Logged
 
Phoner Admin
YaBB Administrator
*****
Offline



Posts: 11753
Location: Germany
Joined: 12. Oct 2003
Gender: Male
Re: Probleme mit Phoner
Reply #3 - 02. Mar 2008 at 16:28
Print Post  
Lass mal testhalber den STUN-Server weg - trag also in das entsprechende Feld nichts ein.
  
Back to top
WWW  
IP Logged
 
Bravosix
YaBB Newbies
*
Offline


Phoner ist großartig!

Posts: 4
Joined: 02. Mar 2008
Re: Probleme mit Phoner
Reply #4 - 04. Mar 2008 at 07:55
Print Post  
Ohne StunSever tritt genau das gleich Problem auf nach 36 sek 408:Request Timeout
  
Back to top
 
IP Logged
 
Phoner Admin
YaBB Administrator
*****
Offline



Posts: 11753
Location: Germany
Joined: 12. Oct 2003
Gender: Male
Re: Probleme mit Phoner
Reply #5 - 05. Apr 2008 at 18:05
Print Post  
Ich kann das bei mir leider absolut nicht nachvollziehen. Hast du noch so eine Personal Firewall installiert, also z.B. ZoneAlarm?
  
Back to top
WWW  
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint