Ok,

it seems that you should set serve and proxy as sip.1und1.de
realm 1und1.de
username as your phone number


Thanks
Vadim

Le 2 avr. 2011 à 03:40, Axel Huizinga a écrit :

> Am 02.04.2011 02:37, schrieb Vadim Lebedev:
>> 
>> Can you post wireshark log of sucessful connection to your provider wit any 
>> other sip phone?
>> 
>> Thanks
>> Vadim
>> Le 31 mars 2011 à 08:40, Axel Huizinga a écrit :
>> 
>>> Hi to all,
>>> am just trying to checkout qutecom but struggle to get it work with my 
>>> provider.
>>> Did anyone succeed using it with an 1und1 account and Fritz!box modem?
>>> 
>>> Cordially,
>>> Axel
>>> _______________________________________________
>>> QuteCom-dev mailing list
>>> QuteCom-dev@lists.qutecom.org
>>> http://lists.qutecom.org/mailman/listinfo/qutecom-dev
>> 
> Hi Vadim,
> I actually use the 1&1 SoftPhone which produces this log on startup:
> 
> Version 2.60.1179
>  
> 02.04.2011 03:16:59.296 Status:
> Initialisierung...
> 
> 02.04.2011 03:16:59.296 Status:
> Netzwerk wird untersucht...
> 
> 02.04.2011 03:17:01.828 Status:
> Netzwerk in Ordnung
> 
> 02.04.2011 03:17:01.890 Status:
> Anmelden am Server...
> 
> 02.04.2011 03:17:02.265 SIP-Nachricht gesendet an 212.227.18.204:5060:
> REGISTER sip:sip.1und1.de SIP/2.0
> To: "0049 6542969320"<sip:496542969...@sip.1und1.de>
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;branch=z9hG4bK-c87542-74187100-1--c87542-;rport
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 1 REGISTER
> Max-Forwards: 70
> User-Agent: 1&1 SoftPhone 2.60.1179
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:02.359 SIP-Nachricht empfangen von 212.227.18.204:5060:
> SIP/2.0 401 Unauthorized
> To: "0049 
> 6542969320"<sip:496542969...@sip.1und1.de>;tag=f8f2ab2c1295e90ed7dbb499b30f44b2.8c6a
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;received=84.166.3.126;branch=z9hG4bK-c87542-74187100-1--c87542-;rport=5070
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 1 REGISTER
> WWW-Authenticate: Digest realm="1und1.de", 
> nonce="4d9679304dc5083ba3338d8c4cda1eeaf3710b6b"
> Server: UI Kamailio
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:02.562 SIP-Nachricht gesendet an 212.227.18.204:5060:
> REGISTER sip:sip.1und1.de SIP/2.0
> To: "0049 6542969320"<sip:496542969...@sip.1und1.de>
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;branch=z9hG4bK-c87542-308635243-1--c87542-;rport
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 2 REGISTER
> Max-Forwards: 70
> User-Agent: 1&1 SoftPhone 2.60.1179
> Authorization: Digest 
> username="496542969320",realm="1und1.de",nonce="4d9679304dc5083ba3338d8c4cda1eeaf3710b6b",uri="sip:sip.1und1.de",response="369f7df33accade56debc6d7f7d30f70",algorithm=MD5
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:02.671 SIP-Nachricht empfangen von 212.227.18.204:5060:
> SIP/2.0 200 OK
> To: "0049 
> 6542969320"<sip:496542969...@sip.1und1.de>;tag=bbd8f31c58bc6a3266ec5509a254d55b-6725
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;received=84.166.3.126;branch=z9hG4bK-c87542-308635243-1--c87542-;rport=5070
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 2 REGISTER
> Contact: 
> <sip:496542969320@84.166.3.126;uniq=E62E891B5B33CBDD696A6827E46CE>;expires=13894,
>  <sip:496542969320@84.166.3.126:5070;site=10BC4761C0CDF573>;expires=13923
> Server: UI Kamailio
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:02.875 SIP-Nachricht gesendet an 212.227.18.204:5060:
> REGISTER sip:sip.1und1.de SIP/2.0
> To: "0049 6542969320"<sip:496542969...@sip.1und1.de>
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;branch=z9hG4bK-c87542-550193605-1--c87542-;rport
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 3 REGISTER
> Contact: <sip:496542969320@84.166.3.126:5070;site=10BC4761C0CDF573>;expires=0
> Max-Forwards: 70
> User-Agent: 1&1 SoftPhone 2.60.1179
> Authorization: Digest 
> username="496542969320",realm="1und1.de",nonce="4d9679304dc5083ba3338d8c4cda1eeaf3710b6b",uri="sip:sip.1und1.de",response="369f7df33accade56debc6d7f7d30f70",algorithm=MD5
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:02.984 SIP-Nachricht empfangen von 212.227.18.204:5060:
> SIP/2.0 200 OK
> To: "0049 
> 6542969320"<sip:496542969...@sip.1und1.de>;tag=bbd8f31c58bc6a3266ec5509a254d55b-55ed
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;received=84.166.3.126;branch=z9hG4bK-c87542-550193605-1--c87542-;rport=5070
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 3 REGISTER
> Contact: 
> <sip:496542969320@84.166.3.126;uniq=E62E891B5B33CBDD696A6827E46CE>;expires=13894
> Server: UI Kamailio
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:03.187 SIP-Nachricht gesendet an 212.227.18.204:5060:
> REGISTER sip:sip.1und1.de SIP/2.0
> To: "0049 6542969320"<sip:496542969...@sip.1und1.de>
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;branch=z9hG4bK-c87542-432020966-1--c87542-;rport
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 4 REGISTER
> Contact: "0049 
> 6542969320"<sip:496542969320@84.166.3.126:5070;site=10BC4761C0CDF573>;expires=3600
> Expires: 3600
> Max-Forwards: 70
> User-Agent: 1&1 SoftPhone 2.60.1179
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:03.281 SIP-Nachricht empfangen von 212.227.18.204:5060:
> SIP/2.0 401 Unauthorized
> To: "0049 
> 6542969320"<sip:496542969...@sip.1und1.de>;tag=f8f2ab2c1295e90ed7dbb499b30f44b2.92c8
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;received=84.166.3.126;branch=z9hG4bK-c87542-432020966-1--c87542-;rport=5070
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 4 REGISTER
> WWW-Authenticate: Digest realm="1und1.de", 
> nonce="4d967931d188359b193e7dc36a1854e5b803ac12"
> Server: UI Kamailio
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:03.484 SIP-Nachricht gesendet an 212.227.18.204:5060:
> REGISTER sip:sip.1und1.de SIP/2.0
> To: "0049 6542969320"<sip:496542969...@sip.1und1.de>
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;branch=z9hG4bK-c87542-281566417-1--c87542-;rport
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 5 REGISTER
> Contact: "0049 
> 6542969320"<sip:496542969320@84.166.3.126:5070;site=10BC4761C0CDF573>;expires=3600
> Expires: 3600
> Max-Forwards: 70
> User-Agent: 1&1 SoftPhone 2.60.1179
> Authorization: Digest 
> username="496542969320",realm="1und1.de",nonce="4d967931d188359b193e7dc36a1854e5b803ac12",uri="sip:sip.1und1.de",response="4fa46452b86b6b1c27734003eadb00e0",algorithm=MD5
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:04.468 Status:
> Verbindung 1: Bereit
> 
> 02.04.2011 03:17:04.468 Status:
> Verbindung 2: Bereit
> 
> 02.04.2011 03:17:03.593 SIP-Nachricht empfangen von 212.227.18.204:5060:
> SIP/2.0 200 OK
> To: "0049 
> 6542969320"<sip:496542969...@sip.1und1.de>;tag=bbd8f31c58bc6a3266ec5509a254d55b-b966
> From: "0049 6542969320"<sip:496542969...@sip.1und1.de>;tag=4257904e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;received=84.166.3.126;branch=z9hG4bK-c87542-281566417-1--c87542-;rport=5070
> Call-ID: 6ffab7e8bc75d14e8edeeb7231cea75c
> CSeq: 5 REGISTER
> Contact: 
> <sip:496542969320@84.166.3.126;uniq=E62E891B5B33CBDD696A6827E46CE>;expires=13893,
>  <sip:496542969320@84.166.3.126:5070;site=10BC4761C0CDF573>;expires=14400
> Server: UI Kamailio
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:04.578 SIP-Nachricht gesendet an 212.227.18.204:5060:
> SUBSCRIBE sip:496542969...@sip.1und1.de:5060 SIP/2.0
> To: <sip:496542969...@sip.1und1.de:5060>
> From: <sip:496542969...@sip.1und1.de:5060>;tag=ed65b22e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;branch=z9hG4bK-c87542-98510885-1--c87542-;rport
> Call-ID: 8d8984b8e22ecf41990cbd685587bdd9
> CSeq: 1 SUBSCRIBE
> Contact: "0049 6542969320"<sip:496542969320@84.166.3.126:5070>
> Expires: 3600
> Max-Forwards: 70
> Accept: application/simple-message-summary
> User-Agent: 1&1 SoftPhone 2.60.1179
> Event: message-summary
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:04.687 SIP-Nachricht empfangen von 212.227.18.204:5060:
> SIP/2.0 401 Unauthorized
> To: 
> <sip:496542969...@sip.1und1.de:5060>;tag=458fb4012080e656b6742c09466dabcd.ecb7
> From: <sip:496542969...@sip.1und1.de:5060>;tag=ed65b22e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;received=84.166.3.126;branch=z9hG4bK-c87542-98510885-1--c87542-;rport=5070
> Call-ID: 8d8984b8e22ecf41990cbd685587bdd9
> CSeq: 1 SUBSCRIBE
> WWW-Authenticate: Digest realm="1und1.de", 
> nonce="4d967932000112c0a1a44ef56e601b13b66a845232c5b7df", qop="auth"
> Server: UI Kamailio
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:04.890 SIP-Nachricht gesendet an 212.227.18.204:5060:
> SUBSCRIBE sip:496542969...@sip.1und1.de:5060 SIP/2.0
> To: <sip:496542969...@sip.1und1.de:5060>
> From: <sip:496542969...@sip.1und1.de:5060>;tag=ed65b22e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;branch=z9hG4bK-c87542-247209296-1--c87542-;rport
> Call-ID: 8d8984b8e22ecf41990cbd685587bdd9
> CSeq: 2 SUBSCRIBE
> Contact: "0049 6542969320"<sip:496542969320@84.166.3.126:5070>
> Expires: 3600
> Max-Forwards: 70
> Accept: application/simple-message-summary
> User-Agent: 1&1 SoftPhone 2.60.1179
> Authorization: Digest 
> username="496542969320",realm="1und1.de",nonce="4d967932000112c0a1a44ef56e601b13b66a845232c5b7df",uri="sip:496542969...@sip.1und1.de:5060",response="0ae43e1404e4e8cae3a0da054623be0a",cnonce="",nc=00000001,qop=auth,algorithm=MD5
> Event: message-summary
> Content-Length: 0
> 
> 
> 02.04.2011 03:17:04.984 SIP-Nachricht empfangen von 212.227.18.204:5060:
> SIP/2.0 404 Not Found
> To: 
> <sip:496542969...@sip.1und1.de:5060>;tag=4ceeccba16a5ac3c25ecfd8a0c2542e2-38bd
> From: <sip:496542969...@sip.1und1.de:5060>;tag=ed65b22e
> Via: SIP/2.0/UDP 
> 84.166.3.126:5070;received=84.166.3.126;branch=z9hG4bK-c87542-247209296-1--c87542-;rport=5070
> Call-ID: 8d8984b8e22ecf41990cbd685587bdd9
> CSeq: 2 SUBSCRIBE
> Server: UI Kamailio
> Content-Length: 0
> 
> 
> 
> 
> 

_______________________________________________
QuteCom-dev mailing list
QuteCom-dev@lists.qutecom.org
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to