keine direkte Registrierung bei Sipgate möglich wenn VCM akt

Forum zu LANCOM Systems VoIP Router/Gateways und zur LANCOM VoIP Option

Moderator: Lancom-Systems Moderatoren

Antworten
cgdu
Beiträge: 71
Registriert: 07 Jun 2005, 08:39

keine direkte Registrierung bei Sipgate möglich wenn VCM akt

Beitrag von cgdu »

Hallo,
bis jetzt habe ich alles im VCM eingstellt und es lief auch ohne Probleme:

mehrere ISDN Leitung, 2 SIP Leitungen bei Sipgate, abgebildet auf mehrere Benutze mit Call Routing....

jetzt kam ich in die Verlegenheit auf einem SNOM 370 einen weiteren Einzel Acoount einrichten zu müssen. Hier scheitert die Registrieung aber.
Sobald ich den VCM deaktiviere kann eine Registrierung erfolgen ohne das ich was an der Konfig des Snom ändere.
Sobald der VCM wieder aktiviert ist, ist keine (Re)Registrierung mehr möglich.

Was müsste ich denn einstellen, damit die Registrierung auch mit eingeschaltetem VCM funktioniert?

VCM off, Sipregistrierung des SNOM:

Code: Alles auswählen

Sent to udp:172.17.6.1:5060 at 25/5/2012 20:07:24:942 (470 bytes):

REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-5a5auodvq980;rport
From: "meineSipID" <sip:meineSipID@sipgate.de>;tag=lt9dh3dhjg
To: "meineSipID" <sip:meineSipID@sipgate.de>
Call-ID: 386d43ade152-6abnbzg9wtz6
CSeq: 10 REGISTER
Max-Forwards: 70
Contact: <sip:meineSipID@172.17.6.81:5160;line=7uzr5rud>;reg-id=1;q=1.0
User-Agent: snom370/8.7.3.7
Allow-Events: dialog
X-Real-IP: 172.17.6.81
Supported: path
Expires: 3600
Content-Length: 0

Sent to udp:217.10.79.9:5060 at 25/5/2012 20:07:25:324 (470 bytes):

REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-5a5auodvq980;rport
From: "meineSipID" <sip:meineSipID@sipgate.de>;tag=lt9dh3dhjg
To: "meineSipID" <sip:meineSipID@sipgate.de>
Call-ID: 386d43ade152-6abnbzg9wtz6
CSeq: 10 REGISTER
Max-Forwards: 70
Contact: <sip:meineSipID@172.17.6.81:5160;line=7uzr5rud>;reg-id=1;q=1.0
User-Agent: snom370/8.7.3.7
Allow-Events: dialog
X-Real-IP: 172.17.6.81
Supported: path
Expires: 3600
Content-Length: 0

Received from udp:217.10.79.9:5060 at 25/5/2012 20:07:25:353 (433 bytes):

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.17.6.81:5160;received=79.227.92.92;branch=z9hG4bK-5a5auodvq980;rport=61032
From: "meineSipID" <sip:meineSipID@sipgate.de>;tag=lt9dh3dhjg
To: "meineSipID" <sip:meineSipID@sipgate.de>;tag=6d6e7f8f352adddb20da2b196524dfa8.8541
Call-ID: 386d43ade152-6abnbzg9wtz6
CSeq: 10 REGISTER
WWW-Authenticate: Digest realm="sipgate.de", nonce="4fbfccb66c5a2a6987e77dd4b3ef0c2a52b7ecc6"
Content-Length: 0

Sent to udp:217.10.79.9:5060 at 25/5/2012 20:07:25:380 (659 bytes):

REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-25nrzs1thz87;rport
From: "meineSipID" <sip:meineSipID@sipgate.de>;tag=lt9dh3dhjg
To: "meineSipID" <sip:meineSipID@sipgate.de>
Call-ID: 386d43ade152-6abnbzg9wtz6
CSeq: 11 REGISTER
Max-Forwards: 70
Contact: <sip:meineSipID@172.17.6.81:5160;line=7uzr5rud>;reg-id=1;q=1.0
User-Agent: snom370/8.7.3.7
Allow-Events: dialog
X-Real-IP: 172.17.6.81
Supported: path
Authorization: Digest username="meineSipID",realm="sipgate.de",nonce="4fbfccb66c5a2a6987e77dd4b3ef0c2a52b7ecc6",uri="sip:sipgate.de",response="a602ccffb14e71504645e6e6e0d1b3f5",algorithm=MD5
Expires: 3600
Content-Length: 0

Received from udp:217.10.79.9:5060 at 25/5/2012 20:07:25:412 (529 bytes):

SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.17.6.81:5160;received=79.227.92.92;branch=z9hG4bK-25nrzs1thz87;rport=61032
From: "meineSipID" <sip:meineSipID@sipgate.de>;tag=lt9dh3dhjg
To: "meineSipID" <sip:meineSipID@sipgate.de>;tag=6d6e7f8f352adddb20da2b196524dfa8.fc39
Call-ID: 386d43ade152-6abnbzg9wtz6
CSeq: 11 REGISTER
Contact: <sip:meineSipID@172.17.6.81:5160;line=dee71cqw>;q=1;expires=520;received="sip:79.227.92.92:61032", <sip:meineSipID@172.17.6.81:5160;line=7uzr5rud>;q=1;expires=600;received="sip:79.227.92.92:61032"
Content-Length: 0

Sent to udp:172.17.6.1:5060 at 25/5/2012 20:07:26:491 (476 bytes):

SUBSCRIBE sip:50000@sipgate.de;user=phone SIP/2.0
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-rqil7hty9u9x;rport
From: <sip:meineSipID@sipgate.de>;tag=39zaralopk
To: <sip:50000@sipgate.de;user=phone>
Call-ID: 4fbfca5e722b-gr42gmk26gue
CSeq: 1 SUBSCRIBE
Max-Forwards: 70
Contact: <sip:meineSipID@172.17.6.81:5160;line=7uzr5rud>;reg-id=1
Event: message-summary
Accept: application/simple-message-summary
User-Agent: snom370/8.7.3.7
Expires: 3600
Content-Length: 0

Sent to udp:217.10.79.9:5060 at 25/5/2012 20:07:26:506 (476 bytes):

SUBSCRIBE sip:50000@sipgate.de;user=phone SIP/2.0
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-rqil7hty9u9x;rport
From: <sip:meineSipID@sipgate.de>;tag=39zaralopk
To: <sip:50000@sipgate.de;user=phone>
Call-ID: 4fbfca5e722b-gr42gmk26gue
CSeq: 1 SUBSCRIBE
Max-Forwards: 70
Contact: <sip:meineSipID@172.17.6.81:5160;line=7uzr5rud>;reg-id=1
Event: message-summary
Accept: application/simple-message-summary
User-Agent: snom370/8.7.3.7
Expires: 3600
Content-Length: 0

Received from udp:217.10.79.9:5060 at 25/5/2012 20:07:26:534 (330 bytes):

SIP/2.0 501 Not Implemented
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-rqil7hty9u9x;rport=61032;received=79.227.92.92
From: <sip:meineSipID@sipgate.de>;tag=39zaralopk
To: <sip:50000@sipgate.de;user=phone>;tag=64c295986a77a1f756ad49f3e6513d0d.1c46
Call-ID: 4fbfca5e722b-gr42gmk26gue
CSeq: 1 SUBSCRIBE
Content-Length: 0
VCM on, Sip Registrierung des Snom:

Code: Alles auswählen

Sent to udp:172.17.6.1:5060 at 25/5/2012 20:09:06:986 (470 bytes):

REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-nbv29zk1wxul;rport
From: "meineSipID" <sip:meineSipID@sipgate.de>;tag=07fyefvyhs
To: "meineSipID" <sip:meineSipID@sipgate.de>
Call-ID: 386d43ade152-6abnbzg9wtz6
CSeq: 14 REGISTER
Max-Forwards: 70
Contact: <sip:meineSipID@172.17.6.81:5160;line=jn13wuy0>;reg-id=1;q=1.0
User-Agent: snom370/8.7.3.7
Allow-Events: dialog
X-Real-IP: 172.17.6.81
Supported: path
Expires: 3600
Content-Length: 0

Received from udp:172.17.6.1:5060 at 25/5/2012 20:09:07:278 (503 bytes):

SIP/2.0 401 login needed
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-nbv29zk1wxul;rport
From: "meineSipID"<sip:meineSipID@sipgate.de>;tag=07fyefvyhs
To: "meineSipID"<sip:meineSipID@sipgate.de>;tag=-223558591--244303803
Call-ID: 386d43ade152-6abnbzg9wtz6
CSeq: 14 REGISTER
Max-Forwards: 70
Server: VPNGAR
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS
WWW-Authenticate: Digest realm="sipgate.de",nonce="f7715a687bb8ad343ddc569a1eee2b4d",opaque="",algorithm=MD5
Content-Length: 0

Sent to udp:172.17.6.1:5060 at 25/5/2012 20:09:07:304 (651 bytes):

REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-gp94k4qtnuvk;rport
From: "meineSipID" <sip:meineSipID@sipgate.de>;tag=07fyefvyhs
To: "meineSipID" <sip:meineSipID@sipgate.de>
Call-ID: 386d43ade152-6abnbzg9wtz6
CSeq: 15 REGISTER
Max-Forwards: 70
Contact: <sip:meineSipID@172.17.6.81:5160;line=jn13wuy0>;reg-id=1;q=1.0
User-Agent: snom370/8.7.3.7
Allow-Events: dialog
X-Real-IP: 172.17.6.81
Supported: path
Authorization: Digest username="meineSipID",realm="sipgate.de",nonce="f7715a687bb8ad343ddc569a1eee2b4d",uri="sip:sipgate.de",response="28031ac00526ee03541e8a454f36b1d3",algorithm=MD5
Expires: 3600
Content-Length: 0

Received from udp:172.17.6.1:5060 at 25/5/2012 20:09:07:334 (390 bytes):

SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-gp94k4qtnuvk;rport
From: "meineSipID"<sip:meineSipID@sipgate.de>;tag=07fyefvyhs
To: "meineSipID"<sip:meineSipID@sipgate.de>;tag=-223558591--244303803
Call-ID: 386d43ade152-6abnbzg9wtz6
CSeq: 15 REGISTER
Max-Forwards: 70
Server: VPNGAR
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS
Content-Length: 0
Sip Trace des Lancom:

Code: Alles auswählen

[SIP-Packet] 2012/05/25 20:08:10,890 [PACKET] :
Receiving datagram with length 470 from 172.17.6.81:5160 to 172.17.6.1:5060
REGISTER sip:sipgate.de SIP/2.0\r\n
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-nbv29zk1wxul;rport\r\n
From: "meineSipID" <sip:meineSipID@sipgate.de>;tag=07fyefvyhs\r\n
To: "meineSipID" <sip:meineSipID@sipgate.de>\r\n
Call-ID: 386d43ade152-6abnbzg9wtz6\r\n
CSeq: 14 REGISTER\r\n
Max-Forwards: 70\r\n
Contact: <sip:meineSipID@172.17.6.81:5160;line=jn13wuy0>;reg-id=1;q=1.0\r\n
User-Agent: snom370/8.7.3.7\r\n
Allow-Events: dialog\r\n
X-Real-IP: 172.17.6.81\r\n
Supported: path\r\n
Expires: 3600\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2012/05/25 20:08:10,890 [PACKET] :
Sending datagram with length 503 from 172.17.6.1:5060 to 172.17.6.81:5160
SIP/2.0 401 login needed\r\n
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-nbv29zk1wxul;rport\r\n
From: "meineSipID"<sip:meineSipID@sipgate.de>;tag=07fyefvyhs\r\n
To: "meineSipID"<sip:meineSipID@sipgate.de>;tag=-223558591--244303803\r\n
Call-ID: 386d43ade152-6abnbzg9wtz6\r\n
CSeq: 14 REGISTER\r\n
Max-Forwards: 70\r\n
Server: VPNGAR\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
WWW-Authenticate: Digest realm="sipgate.de",nonce="f7715a687bb8ad343ddc569a1eee2b4d",opaque="",algorithm=MD5\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2012/05/25 20:08:11,200 [PACKET] :
Receiving datagram with length 651 from 172.17.6.81:5160 to 172.17.6.1:5060
REGISTER sip:sipgate.de SIP/2.0\r\n
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-gp94k4qtnuvk;rport\r\n
From: "meineSipID" <sip:meineSipID@sipgate.de>;tag=07fyefvyhs\r\n
To: "meineSipID" <sip:meineSipID@sipgate.de>\r\n
Call-ID: 386d43ade152-6abnbzg9wtz6\r\n
CSeq: 15 REGISTER\r\n
Max-Forwards: 70\r\n
Contact: <sip:meineSipID@172.17.6.81:5160;line=jn13wuy0>;reg-id=1;q=1.0\r\n
User-Agent: snom370/8.7.3.7\r\n
Allow-Events: dialog\r\n
X-Real-IP: 172.17.6.81\r\n
Supported: path\r\n
Authorization: Digest username="meineSipID",realm="sipgate.de",nonce="f7715a687bb8ad343ddc569a1eee2b4d",uri="sip:sipgate.de",response="28031ac00526ee03541e8a454f36b1d3",algorithm=MD5\r\n
Expires: 3600\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2012/05/25 20:08:11,230 [PACKET] :
Sending datagram with length 390 from 172.17.6.1:5060 to 172.17.6.81:5160
SIP/2.0 403 Forbidden\r\n
Via: SIP/2.0/UDP 172.17.6.81:5160;branch=z9hG4bK-gp94k4qtnuvk;rport\r\n
From: "meineSipID"<sip:meineSipID@sipgate.de>;tag=07fyefvyhs\r\n
To: "meineSipID"<sip:meineSipID@sipgate.de>;tag=-223558591--244303803\r\n
Call-ID: 386d43ade152-6abnbzg9wtz6\r\n
CSeq: 15 REGISTER\r\n
Max-Forwards: 70\r\n
Server: VPNGAR\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS\r\n
Content-Length: 0\r\n
\r\n
Gruß
Christian
backslash
Moderator
Moderator
Beiträge: 7129
Registriert: 08 Nov 2004, 21:26
Wohnort: Aachen

Beitrag von backslash »

Hi cgdu

das ist ein unschönes Feature, das sich leider nicht abschalten läßt... Der DNS-Server des LANCOMs beantwortet alle SRV-Anfragen für den vom VCM genutzten Provider mit der IP des LANCOMs, damit eixistierende Umgebungen nicht umkonfiguriert werden müssen...

Du hast zwei Möglichkeiten: Im VCM einen anderen Provider nutzen, oder am SNOM-Telefon einen anderen DNS-Server als das LANCOM eintragen...

Gruß
Backslash
Antworten