06. May 2024 at 01:52
 Choose Language:
  Phoner(Lite) Forum › Allgemein / General › PhonerLite › Phoner lite / Kein Verbindungsaufbau
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: 1 Send TopicPrint
Hot Topic (More than 10 Replies) Phoner lite / Kein Verbindungsaufbau (Read 10611 times)
Hazel
YaBB Newbies
*
Offline



Posts: 11
Joined: 08. Feb 2008
Gender: Male
Phoner lite / Kein Verbindungsaufbau
10. Feb 2008 at 21:27
Print Post  
Hallo alle zusammen,
ich bin neu hier und habe so gut wie keine Ahnung was das Konfigurieren von Softphones angeht. Bitte entschuldigt deshalb wenn ich mich umständlich ausdrücke.
Zu meinem Problem mit Phone Lite:
Ich bekomme keine ausgehende Verbindung hin. Eingehende Verbindungen werden im Fenster "codec" mit: in:--,out:A-Law bezeichnet.
Zu Phone  Lite und speziell zu dieser Meldung habe ich hier schon einiges gefunden, aber nichts hilft mir wirklich weiter.
Es wäre nett wenn mir einer von euch helfen könnte.

Zu meinem System:
Phone Lite1.4.1; System: Win XP SP2; Router: FritzBox 7150 über Switch; Provider: 1&1 

Gruß
HInrich
« Last Edit: 11. Feb 2008 at 21:41 by Hazel »  
Back to top
Skype/VoIP  
IP Logged
 
Phoner Admin
YaBB Administrator
*****
Offline



Posts: 11421
Location: Germany
Joined: 12. Oct 2003
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #1 - 14. Feb 2008 at 19:25
Print Post  
Du müsstest mir mal den Inhalt des Debug-Fensters (Menü: Hilfe/Debug) nach einem solchen Vorgang per Mail zusenden.
  
Back to top
WWW  
IP Logged
 
Hazel
YaBB Newbies
*
Offline



Posts: 11
Joined: 08. Feb 2008
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #2 - 14. Feb 2008 at 21:41
Print Post  
Hallo, 
nett das Du dich meldest. Ich habe heute keine Zeit mehr, melde mich morgen.
Gruß
Hinrich
  
Back to top
Skype/VoIP  
IP Logged
 
Hazel
YaBB Newbies
*
Offline



Posts: 11
Joined: 08. Feb 2008
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #3 - 17. Feb 2008 at 18:52
Print Post  
Hallo,
hat leider ein bisschen gedauert, aber ich binberuflich zur Zeit sehr eingespannt. 
Hier meine Debug Liste von einem (Versuch) Anruf:
-------------------------------------------
18:49:01,937: T: 212.227.15.231:5060 (UDP)
INVITE sip:051523297@1und1.de SIP/2.0
Via: SIP/2.0/UDP 77.187.199.254:62822;branch=z9hG4bK00536341eedbdc11b1e50015f2379de6;rport
From: "107 Laptop" <sip:495152979107@1und1.de>;tag=3844365636
To: <sip:051523297@1und1.de>
Call-ID: 00536341-EEDB-DC11-B1E4-0015F2379DE6@77.187.199.254
CSeq: 6 INVITE
Contact: <sip:495152979107@77.187.199.254:62822>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length:   370

v=0
o=- 2454637954 0 IN IP4 77.187.199.254
s=SIPPER for PhonerLite
c=IN IP4 77.187.199.254
t=0 0
m=audio 62823 RTP/AVP 8 0 2 3 97 110 9 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:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
18:49:10,390: Disconnect Request: 0D 00 01 00 04 80 14 00 01 01 00 00 00 
18:49:10,390: Disconnect Request
18:49:10,390: Disconnect Confirm: 0E 00 01 00 04 81 14 00 01 01 00 00 00 00 
18:49:10,406: Disconnect Confirm
18:49:10,406: Disconnect Indication: 0E 00 01 00 04 82 A6 00 01 01 00 00 00 34 
18:49:10,406: Disconnect Indication: 
18:49:10,406: Disconnect Response: 0C 00 01 00 04 83 A6 00 01 01 00 00 
18:49:10,406: Disconnect Response
  
Back to top
Skype/VoIP  
IP Logged
 
Phoner Admin
YaBB Administrator
*****
Offline



Posts: 11421
Location: Germany
Joined: 12. Oct 2003
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #4 - 19. Feb 2008 at 07:51
Print Post  
Als "Registrar/Proxy" hast du aber schon "sip.1und1.de" angegeben?
  
Back to top
WWW  
IP Logged
 
Hazel
YaBB Newbies
*
Offline



Posts: 11
Joined: 08. Feb 2008
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #5 - 20. Feb 2008 at 14:14
Print Post  
Ich habe noch ein bißchen rumprobiert. Dabei ergab sich folgendes:

in der Frittzbox hatte ich die Softphone-Telefonnummer registriert. Nachdem ich diese deaktiviert hatte konnte ich zumindest das Softphone anrufen.Ausgehende Verbindungen sind immer noch nicht möglich.

Die Servereinstellungen lauten:
Proxy:  sip:1und1.de
Stun:   stun.1und1.de
Domain: 1und1.de

Netzwerk:
Lokal. Port:   5061 (auch in der Box freigeschaltet) bei Freischaltung von Port 5060 meckert die Fritzbox :"Kollision mit interner Regel" Uaf 5060 gibt es auch gar keine Verbindung.
Ich hänge Dir noch einmal die DEbugg Liste mit je einem -anruf und einem ausgehenden Ruf an
-------------------------------------------
14:13:24,468: R: 212.227.15.197:5060 (UDP)
INVITE sip:495152979107@77.187.217.14:5061 SIP/2.0
Record-Route: <sip:212.227.15.194;ftag=92D17A96BD720F91;lr=on>
Via: SIP/2.0/UDP 212.227.15.197;branch=z9hG4bKda4f96378b2b0f2fe033def773715cf5
Via: SIP/2.0/UDP 212.227.15.194;branch=z9hG4bK7de3.4b6349c3.0
Via: SIP/2.0/UDP 212.227.15.231;branch=z9hG4bK56997a51f56ae0ff051796e99856c4d4
Via: SIP/2.0/UDP 77.187.217.14:5060;branch=z9hG4bK227695038F9D2135
From: <sip:495152979105@1und1.de>;tag=92D17A96BD720F91
To: <sip:495152979107@1und1.de>
Call-ID: A87DF95255D957A0@77.187.217.14
CSeq: 154 INVITE
Contact: <sip:495152979105@77.187.217.14;uniq=641D28F28F3D78AFEAF853CC1B2DD>
Max-Forwards: 14
Expires: 120
User-Agent: AVM FRITZ!Box Fon WLAN 7050 (UI) 14.04.33 (May 10 2007)
Supported: 100rel,replaces,timer
Allow-Events: telephone-event,refer
Allow: INVITE,ACK,OPTIONS,CANCEL,BYE,UPDATE,PRACK,INFO,SUBSCRIBE,NOTIFY,REFER,MESSAGE
Content-Type: application/sdp
Accept: application/sdp, multipart/mixed
Accept-Encoding: identity
Content-Length:   359
P-Asserted-Identity: <sip:495152979105@1und1.de>

v=0
o=user 8952859 8952859 IN IP4 77.187.217.14
s=call
c=IN IP4 77.187.217.14
t=0 0
m=audio 7082 RTP/AVP 8 0 2 102 100 99 97 101
a=sendrecv
a=rtpmap:2 G726-32/8000
a=rtpmap:102 G726-32/8000
a=rtpmap:100 G726-40/8000
a=rtpmap:99 G726-24/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-11
a=rtcp:7083

-------------------------------------------
14:13:24,484: T: 212.227.15.200:3478
STUN requesting...
-------------------------------------------
14:13:24,531: T: 212.227.15.200:3478
STUN
  public ip: 77.187.217.14:62732


-------------------------------------------
14:13:24,609: Connect Indication: 43 00 01 00 02 82 2B 00 01 01 00 00 01 00 16 80 34 39 35 31 35 32 39 37 39 31 30 37 40 31 75 6E 64 31 2E 64 65 17 00 80 34 39 35 31 35 32 39 37 39 31 30 35 40 31 75 6E 64 31 2E 64 65 00 00 00 00 00 00 
14:13:24,609: Connect Indication
14:13:24,609:  CIP: 1 (speech)
14:13:24,609:  CalledPartyNumber: 495152979107@1und1.de
14:13:24,609:  CallingPartyNumber: 495152979105@1und1.de
14:13:24,609: Alert Request: 0D 00 01 00 01 80 C8 07 01 01 00 00 00 
14:13:24,609: Alert Request
-------------------------------------------
14:13:24,609: T: 212.227.15.197:5060 (UDP)
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 212.227.15.197;branch=z9hG4bKda4f96378b2b0f2fe033def773715cf5
Via: SIP/2.0/UDP 212.227.15.194;branch=z9hG4bK7de3.4b6349c3.0
Via: SIP/2.0/UDP 212.227.15.231;branch=z9hG4bK56997a51f56ae0ff051796e99856c4d4
Via: SIP/2.0/UDP 77.187.217.14:5060;branch=z9hG4bK227695038F9D2135
Record-Route: <sip:212.227.15.194;ftag=92D17A96BD720F91;lr=on>
From: <sip:495152979105@1und1.de>;tag=92D17A96BD720F91
To: <sip:495152979107@1und1.de>
Call-ID: A87DF95255D957A0@77.187.217.14
CSeq: 154 INVITE
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length: 0


-------------------------------------------
14:13:24,875: Alert Confirm: 0E 00 01 00 01 81 C8 07 01 01 00 00 00 00 
14:13:24,890: Alert Confirm
-------------------------------------------
14:13:24,609: T: 212.227.15.197:5060 (UDP)
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 212.227.15.197;branch=z9hG4bKda4f96378b2b0f2fe033def773715cf5
Via: SIP/2.0/UDP 212.227.15.194;branch=z9hG4bK7de3.4b6349c3.0
Via: SIP/2.0/UDP 212.227.15.231;branch=z9hG4bK56997a51f56ae0ff051796e99856c4d4
Via: SIP/2.0/UDP 77.187.217.14:5060;branch=z9hG4bK227695038F9D2135
Record-Route: <sip:212.227.15.194;ftag=92D17A96BD720F91;lr=on>
From: <sip:495152979105@1und1.de>;tag=92D17A96BD720F91
To: <sip:495152979107@1und1.de>;tag=0072bf4823dedc11be3e0015f2379de6
Call-ID: A87DF95255D957A0@77.187.217.14
CSeq: 154 INVITE
Contact: <sip:495152979107@77.187.217.14:5061>
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length: 0


-------------------------------------------
14:13:30,062: Connect Response: 33 00 01 00 02 83 2B 00 01 01 00 00 03 00 09 01 00 01 00 00 00 00 00 00 17 00 80 34 39 35 31 35 32 39 37 39 31 30 37 40 31 75 6E 64 31 2E 64 65 00 00 00 
14:13:30,062: Connect Response: reject call, user busy
14:13:30,062: Disconnect Indication: 0E 00 01 00 04 82 36 00 01 01 00 00 00 34 
14:13:30,062: Disconnect Indication: 
14:13:30,062: Disconnect Response: 0C 00 01 00 04 83 36 00 01 01 00 00 
14:13:30,062: Disconnect Response
-------------------------------------------
14:13:30,062: T: 212.227.15.197:5060 (UDP)
SIP/2.0 486 Busy Here
Via: SIP/2.0/UDP 212.227.15.197;branch=z9hG4bKda4f96378b2b0f2fe033def773715cf5
Via: SIP/2.0/UDP 212.227.15.194;branch=z9hG4bK7de3.4b6349c3.0
Via: SIP/2.0/UDP 212.227.15.231;branch=z9hG4bK56997a51f56ae0ff051796e99856c4d4
Via: SIP/2.0/UDP 77.187.217.14:5060;branch=z9hG4bK227695038F9D2135
Record-Route: <sip:212.227.15.194;ftag=92D17A96BD720F91;lr=on>
From: <sip:495152979105@1und1.de>;tag=92D17A96BD720F91
To: <sip:495152979107@1und1.de>;tag=0072bf4823dedc11be3e0015f2379de6
Call-ID: A87DF95255D957A0@77.187.217.14
CSeq: 154 INVITE
Contact: <sip:495152979107@77.187.217.14:5061>
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
User-Agent: SIPPER for PhonerLite
Content-Length: 0


-------------------------------------------
14:13:30,140: R: 212.227.15.197:5060 (UDP)
ACK sip:495152979107@77.187.217.14:5061 SIP/2.0
Max-Forwards: 10
Via: SIP/2.0/UDP 212.227.15.197;branch=z9hG4bKda4f96378b2b0f2fe033def773715cf5
Via: SIP/2.0/UDP 212.227.15.194;branch=z9hG4bK7de3.4b6349c3.0
From: <sip:495152979105@1und1.de>;tag=92D17A96BD720F91
Call-ID: A87DF95255D957A0@77.187.217.14
To: <sip:495152979107@1und1.de>;tag=0072bf4823dedc11be3e0015f2379de6
CSeq: 154 ACK
User-Agent: UI OpenSer
Content-Length: 0


-------------------------------------------
14:13:41,078: Connect Request: 46 00 01 00 02 80 C9 07 01 00 00 00 01 00 16 80 34 39 35 31 35 32 39 37 39 31 30 35 40 31 75 6E 64 31 2E 64 65 0E 00 80 34 39 35 31 35 32 39 37 39 31 30 37 00 00 09 01 00 01 00 00 00 00 00 00 00 00 02 91 81 00 
-------------------------------------------
14:13:41,078: R: DNS lookup for '1und1.de'
start resolving...
14:13:41,078: Connect Request: 495152979107 to 495152979105@1und1.de
-------------------------------------------
14:13:41,078: R: DNS lookup for '1und1.de'
212.227.116.117
-------------------------------------------
14:13:41,078: R: DNS lookup for '1und1.de'
start resolving SRV (UDP)...
-------------------------------------------
14:13:41,125: R: DNS lookup for '1und1.de'
212.227.15.197:5060
-------------------------------------------
14:13:41,125: T: 212.227.15.200:3478
STUN requesting...
-------------------------------------------
14:13:41,187: T: 212.227.15.200:3478
STUN
  public ip: 77.187.217.14:62732


-------------------------------------------
14:13:41,250: Connect Confirm: 0E 00 01 00 02 81 C9 07 01 01 00 00 00 00 
14:13:41,250: Connect Confirm
-------------------------------------------
14:13:41,250: T: 212.227.15.197:5060 (UDP)
INVITE sip:495152979105@1und1.de SIP/2.0
Via: SIP/2.0/UDP 77.187.217.14:5061;branch=z9hG4bK8070e15223dedc11be3f0015f2379de6;rport
From: "107 Laptop" <sip:495152979107@1und1.de>;tag=3513059160
To: <sip:495152979105@1und1.de>
Call-ID: 8070E152-23DE-DC11-BE3E-0015F2379DE6@77.187.217.14
CSeq: 3 INVITE
Contact: <sip:495152979107@77.187.217.14:5061>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length:   382

v=0
o=- 1522567223 0 IN IP4 77.187.217.14
s=SIPPER for PhonerLite
c=IN IP4 77.187.217.14
t=0 0
m=audio 62732 RTP/AVP 8 0 2 3 97 110 9 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:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=rtcp:62764
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
14:13:41,765: T: 212.227.15.197:5060 (UDP)
INVITE sip:495152979105@1und1.de SIP/2.0
Via: SIP/2.0/UDP 77.187.217.14:5061;branch=z9hG4bK8070e15223dedc11be3f0015f2379de6;rport
From: "107 Laptop" <sip:495152979107@1und1.de>;tag=3513059160
To: <sip:495152979105@1und1.de>
Call-ID: 8070E152-23DE-DC11-BE3E-0015F2379DE6@77.187.217.14
CSeq: 3 INVITE
Contact: <sip:495152979107@77.187.217.14:5061>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length:   382

v=0
o=- 1522567223 0 IN IP4 77.187.217.14
s=SIPPER for PhonerLite
c=IN IP4 77.187.217.14
t=0 0
m=audio 62732 RTP/AVP 8 0 2 3 97 110 9 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:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=rtcp:62764
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
14:13:42,781: T: 212.227.15.197:5060 (UDP)
INVITE sip:495152979105@1und1.de SIP/2.0
Via: SIP/2.0/UDP 77.187.217.14:5061;branch=z9hG4bK8070e15223dedc11be3f0015f2379de6;rport
From: "107 Laptop" <sip:495152979107@1und1.de>;tag=3513059160
To: <sip:495152979105@1und1.de>
Call-ID: 8070E152-23DE-DC11-BE3E-0015F2379DE6@77.187.217.14
CSeq: 3 INVITE
Contact: <sip:495152979107@77.187.217.14:5061>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length:   382

v=0
o=- 1522567223 0 IN IP4 77.187.217.14
s=SIPPER for PhonerLite
c=IN IP4 77.187.217.14
t=0 0
m=audio 62732 RTP/AVP 8 0 2 3 97 110 9 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:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=rtcp:62764
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
14:13:44,796: T: 212.227.15.197:5060 (UDP)
INVITE sip:495152979105@1und1.de SIP/2.0
Via: SIP/2.0/UDP 77.187.217.14:5061;branch=z9hG4bK8070e15223dedc11be3f0015f2379de6;rport
From: "107 Laptop" <sip:495152979107@1und1.de>;tag=3513059160
To: <sip:495152979105@1und1.de>
Call-ID: 8070E152-23DE-DC11-BE3E-0015F2379DE6@77.187.217.14
CSeq: 3 INVITE
Contact: <sip:495152979107@77.187.217.14:5061>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length:   382

v=0
o=- 1522567223 0 IN IP4 77.187.217.14
s=SIPPER for PhonerLite
c=IN IP4 77.187.217.14
t=0 0
m=audio 62732 RTP/AVP 8 0 2 3 97 110 9 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:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=rtcp:62764
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
14:13:48,812: T: 212.227.15.197:5060 (UDP)
INVITE sip:495152979105@1und1.de SIP/2.0
Via: SIP/2.0/UDP 77.187.217.14:5061;branch=z9hG4bK8070e15223dedc11be3f0015f2379de6;rport
From: "107 Laptop" <sip:495152979107@1und1.de>;tag=3513059160
To: <sip:495152979105@1und1.de>
Call-ID: 8070E152-23DE-DC11-BE3E-0015F2379DE6@77.187.217.14
CSeq: 3 INVITE
Contact: <sip:495152979107@77.187.217.14:5061>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length:   382

v=0
o=- 1522567223 0 IN IP4 77.187.217.14
s=SIPPER for PhonerLite
c=IN IP4 77.187.217.14
t=0 0
m=audio 62732 RTP/AVP 8 0 2 3 97 110 9 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:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=rtcp:62764
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
14:13:56,828: T: 212.227.15.197:5060 (UDP)
INVITE sip:495152979105@1und1.de SIP/2.0
Via: SIP/2.0/UDP 77.187.217.14:5061;branch=z9hG4bK8070e15223dedc11be3f0015f2379de6;rport
From: "107 Laptop" <sip:495152979107@1und1.de>;tag=3513059160
To: <sip:495152979105@1und1.de>
Call-ID: 8070E152-23DE-DC11-BE3E-0015F2379DE6@77.187.217.14
CSeq: 3 INVITE
Contact: <sip:495152979107@77.187.217.14:5061>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length:   382

v=0
o=- 1522567223 0 IN IP4 77.187.217.14
s=SIPPER for PhonerLite
c=IN IP4 77.187.217.14
t=0 0
m=audio 62732 RTP/AVP 8 0 2 3 97 110 9 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:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=rtcp:62764
a=fmtp:101 0-15
a=sendrecv

-------------------------------------------
14:14:12,843: T: 212.227.15.197:5060 (UDP)
INVITE sip:495152979105@1und1.de SIP/2.0
Via: SIP/2.0/UDP 77.187.217.14:5061;branch=z9hG4bK8070e15223dedc11be3f0015f2379de6;rport
From: "107 Laptop" <sip:495152979107@1und1.de>;tag=3513059160
To: <sip:495152979105@1und1.de>
Call-ID: 8070E152-23DE-DC11-BE3E-0015F2379DE6@77.187.217.14
CSeq: 3 INVITE
Contact: <sip:495152979107@77.187.217.14:5061>
Content-Type: application/sdp
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE
Max-Forwards: 70
Supported: 100rel
User-Agent: SIPPER for PhonerLite
Content-Length:   382

v=0
o=- 1522567223 0 IN IP4 77.187.217.14
s=SIPPER for PhonerLite
c=IN IP4 77.187.217.14
t=0 0
m=audio 62732 RTP/AVP 8 0 2 3 97 110 9 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:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=rtcp:62764
a=fmtp:101 0-15
a=sendrecv
-------------------------------------------
14:14:13,265: Disconnect Indication: 0E 00 01 00 04 82 67 00 0
  
Back to top
Skype/VoIP  
IP Logged
 
Phoner Admin
YaBB Administrator
*****
Offline



Posts: 11421
Location: Germany
Joined: 12. Oct 2003
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #6 - 20. Feb 2008 at 20:18
Print Post  
Der Port 5061 ist der Default-Port für SIP über TLS.
Ich würde dir einen anderen Port empfehlen, z.B. Port 5070.
  
Back to top
WWW  
IP Logged
 
Hazel
YaBB Newbies
*
Offline



Posts: 11
Joined: 08. Feb 2008
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #7 - 20. Feb 2008 at 21:53
Print Post  
Habe ich ausprobiert,
das Ergebniss ist das gleiche. Eingehende Gespräche sind möglich, ausgehende Gespräche nicht
  
Back to top
Skype/VoIP  
IP Logged
 
Phoner Admin
YaBB Administrator
*****
Offline



Posts: 11421
Location: Germany
Joined: 12. Oct 2003
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #8 - 20. Feb 2008 at 21:58
Print Post  
Du scheinst als "Registrar/Proxy" den Wert "1und1.de" statt "sip.1und1.de" konfiguriert zu haben!
  
Back to top
WWW  
IP Logged
 
Hazel
YaBB Newbies
*
Offline



Posts: 11
Joined: 08. Feb 2008
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #9 - 21. Feb 2008 at 20:49
Print Post  
Nein, 
Registrar / Proxy Steht auf sip.1und1.de
  
Back to top
Skype/VoIP  
IP Logged
 
Phoner Admin
YaBB Administrator
*****
Offline



Posts: 11421
Location: Germany
Joined: 12. Oct 2003
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #10 - 22. Feb 2008 at 09:09
Print Post  
Quote:
14:13:41,078: R: DNS lookup for '1und1.de'

Das lässt aber eben was anderes vermuten!
  
Back to top
WWW  
IP Logged
 
Hazel
YaBB Newbies
*
Offline



Posts: 11
Joined: 08. Feb 2008
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #11 - 22. Feb 2008 at 18:39
Print Post  
Die Einstellungen sind so wie oben beschrieben.
Ich habe noch etwas anderes versucht:

Phoner Lite    Port                 5070 freigeschaltet Fritzbox / TCP

Fritzbox                               5070 freigeschaltet  aber für UDP

und jetzt lach nicht, die ganze Sache funktioniert. Die Sprache ist noch sehr verzerrt aber immhin klappt die Verbindung über das Kalbel & Mobil (D2)
Gruß, und vielen Dank

Hinrich
  
Back to top
Skype/VoIP  
IP Logged
 
Hazel
YaBB Newbies
*
Offline



Posts: 11
Joined: 08. Feb 2008
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #12 - 27. Feb 2008 at 17:42
Print Post  
So, ein kurze Zusammenstellung der Konfiguration:
System: XP Sp2   
Firewall: Zonealarm
Router:  Fritzbox 7050

Konfiguration:
Fritzbox: Port 5070 auf UDP freigeschaltet 
            !Internetrufnummer des Softphones nicht in der Fritzbox       
            angelegt!

Firewall:  Mittlerer Sicherheitsstatus auf beiden Einstellungen

Phoner-Lite: Port 5070
                 Verbindung TCP (nicht wie in der Fritzbox UDP!)

Mit dieseer Konfiguration habe ich Verbindung in und aus allen Netzen. Die Sprachqulität lässt aber zu wünschen übrig.
Gruß
Hinrich
  
Back to top
Skype/VoIP  
IP Logged
 
Phoner Admin
YaBB Administrator
*****
Offline



Posts: 11421
Location: Germany
Joined: 12. Oct 2003
Gender: Male
Re: Phoner lite / Kein Verbindungsaufbau
Reply #13 - 27. Feb 2008 at 19:09
Print Post  
Die Sprachqualität hängt von mehreren Faktoren ab:
  • Mikrofon
  • Soundkarte
  • verwendeter Codec
  • Internetanbindung, also Bandbreite, Latenz (Ping-Zeiten) und Jitter

Wir müssen zuerst mal dein Problem identifizieren.
  
Back to top
WWW  
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint
‹ Previous Topic | Next Topic ›
 
  « Board Index ‹ Board Top  

Phoner(Lite) Forum » Powered by YaBB 2.6.11!
YaBB Forum Software © 2000-2024. All Rights Reserved.

Valid RSS Valid XHTML Valid CSS Powered by Perl Source Forge