Ein paar Problemchen mit meinem neuen 1722

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

Moderator: Lancom-Systems Moderatoren

Antworten
jhilgers
Beiträge: 175
Registriert: 02 Mär 2005, 14:39
Wohnort: Aachen

Beitrag von jhilgers »

Hi,

langsam bekomme ich graue Haare.

Vielleicht ein bisschen Vorgeschichte:
Ich habe eine russische Telefonnummer bei Libretel, welche auf einen SIP-Provider weitergeleitet wird.
Diese Nummer leite ich normalerweise über FWD weiter. Wenn mich nun jemand anruft, gehe ich dran.... es ist ein paar Sekunden Stille, dann höre ein paar Geräusche und dann steht die Verbindung.

Beim Lancom klingelt das Telefon, ich gehe dran, warte ein paar Sekunden und die Verbindung wird getrennt :-(

Zweiter Versuch SIPGATE:
Telefon klingelt... Ich gehe dran, aber dann nichts mehr. Nur Stille. Bis ich dann plötzlich merke, dass jemand anklopft. Es ist die gleiche Person, jedoch steht die alte Leitung noch. Hier ist auch der Mitschnitt:

[Callmanager] 2006/02/09 19:40:26,270
ClnID From: '82671623'
Convert CldID: '10' ==> CldMSN: '10'
@ sipgate
Callmanager ON @ sipgate
SIP-Packet ON @ sipgate

jhilgers@Lancom1722:/
>
[SIP-Packet] 2006/02/09 19:40:44,370
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/09 19:40:45,520
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/09 19:40:47,520
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/09 19:40:51,520
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/09 19:40:55,520
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/09 19:40:59,520
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/09 19:41:03,520
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/09 19:41:07,520
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/09 19:41:11,520
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/09 19:41:12,520
Sending Datagram with length 402 to 217.10.79.9:5060:
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 84.187.243.68:34351;branch=z9hG4bK-1cc4646c-0e623236
From: <sip:8001960@sipgate.de>;tag=1930531248-965265624
To: <sip:8001960@sipgate.de>
Call-ID: 3861062496@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:8001960@84.187.243.68:34351>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 2006/02/09 19:41:15,520
Sending Datagram with length 987 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK4eba.8d7ad855.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK4eba.c7f3f7a3.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=18c486edc3da5189cf938cb3fa08520c.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=8c4790f2d5f5236b503ff6b2721246e7.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-12ff0b00ffffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ffff0b00ffffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=2065446303-3493239279
Call-ID: 5cac0b00b68ceb108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.243.68:34351>
Content-Type: application/sdp
Content-Length: 140

v=0
o=Lancom 12345 6789 IN IP4 84.187.243.68
s=Lancom PBX
c=IN IP4 84.187.243.68
t=0 0
m=audio 43360 RTP/AVP 8
a=rtpmap:8 PCMA/8000

Ein Anruf von ISDN über VOIP funktioniert mit SIPGATE. Nur beschwert sich der andere Gesprächpartner über sehr schlecht Gesprächsqualität eine starkes Echo. Bei mir ist die Qualität ok.

Brauche dringend Hilfe, da irgendwie VOIP überhaupt nicht so läuft, wie es soll. Muss immer zum Telefonieren meine alte Fritzbox anschliessen :-(

Gruss
Jochen
Nach oben
jhilgers
Beiträge: 175
Registriert: 02 Mär 2005, 14:39
Wohnort: Aachen

Beitrag von jhilgers »

N'abend,

so, habe gerade noch versucht, SIPNET.RU ans laufen zu bekommen. Dass tut einfach nicht. Habe genau die gleichen Felder wie in der Fritzbox ausgefüllt.

Die Registration läuft scheinbar ohne Problem. Sehe aber beim wählen, das das Passwort falsch gemeldet wird.

Bekomme die Krise. Habe schon fast jeden VOIP-Adapter zum Laufen gebracht, aber das Ding will einfach nicht.

Gruss
Jochen
Nach oben
Benutzeravatar
MoinMoin
Moderator
Moderator
Beiträge: 1979
Registriert: 12 Nov 2004, 16:04

Beitrag von MoinMoin »

Moin, moin!

Hast da zu dem Trace auch noch eine Vorgeschichte? Ich sehe nur, daß SipGate des OK ignoriert.

Ciao, Georg
Nach oben
jhilgers
Beiträge: 175
Registriert: 02 Mär 2005, 14:39
Wohnort: Aachen

Beitrag von jhilgers »

Hi Georg,

was willst Du denn genau wissen?

Meine Festnetznummer in St. Petersburg wird wahlweise (konfigurierbar) auf meine Adresse bei Sipgate oder FWD weitergeleitet.
Kommt der Anruf von St. Petersburg über den Provider SIPGATE (oder auch FWD) rein, klingelt es auf der internen MSN 10. Also bis hier ist alles ok.
Hebe ich den Höre ab, höre ich nichts oder besser gesagt Stille. Spätestens aber nach 1 oder 2 Sekunden !!!sollte!!! die Verbindung stehen. Jedoch bleibt die Stille so lange, bis ich aufgelegt habe. Das war auch das Trace, was ich mitgeschickt habe. Und obwohl der andere schon längst aufgelegt hatte, steht die Verbindung immer noch und ich bekomme per Anklopfen nur mit, wie die selbe Person wieder anruft


Wenn ich FWD konfiguriere, wird die Verbindung direkt nach 1 oder 2 Sekunden nach dem Abheben getrennt ( habe leider kein Trace bisher).

Eine aktuelle Konfiguration habe ich Louis geschickt.
Wenn Du noch irgendwelche Traces brauchst, sag bescheid.

Gruss
Jochen
Nach oben
Benutzeravatar
MoinMoin
Moderator
Moderator
Beiträge: 1979
Registriert: 12 Nov 2004, 16:04

Beitrag von MoinMoin »

Moin, moin!
jhilgers hat geschrieben:was willst Du denn genau wissen?
Ich will den kompletten Trace sehen, beginnend mit dem ersten INVITE. Mittendrinn mit dem Trace anzufangen bringt nichts, denn dann ist der Fehler meist schon längst passiert. Woher soll ich denn wissen, warum SipGate das OK ignoriert, wenn ich die Vorgeschichte nicht kenne?

Ciao, Georg
Nach oben
jhilgers
Beiträge: 175
Registriert: 02 Mär 2005, 14:39
Wohnort: Aachen

SIPNET Probleme

Beitrag von jhilgers »

Hier mal das Problem mit SIPNET verglichen mit dem Trace von der Fritzbox.

LANCOM :

Callmanager] 2006/02/10 19:48:21,420
From: 10@intern Line: 'USER.ISDN'
To : 78122671623@intern <Number is complete>
Info: Parse call routing table for active entries
==> From: 10@intern Line: 'USER.ISDN'
To : 78122671623@sipnet.ru Line: 'SIPNET'
InitiateCall: 78122671623@sipnet.ru Line: 'SIPNET'

[SIP-Packet] 2006/02/10 19:48:21,430
Sending Datagram with length 748 to 212.53.35.219:5060:
INVITE sip:78122671623@sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:1678128@84.187.234.252:39395>
Content-Type: application/sdp
Content-Length: 286

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 38918 RTP/AVP 8 0 106 2 104 103
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:106 G726-40/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:104 G726-24/8000
a=rtpmap:103 G726-16/8000


[SIP-Packet] 2006/02/10 19:48:21,600
Receiving Datagram with length 321 from 212.53.35.219:5060:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:21,610
Receiving Datagram with length 480 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>;tag=2B29B9AB28E44317
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="FF95E4DEB4B9D991FBD2",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:21,610
Sending Datagram with length 590 to 212.53.35.219:5060:
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-b33aa419-b425d12c
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: "1678128" <sip:1678128@sipnet.ru>
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:1678128@84.187.234.252:39395>
Expires: 0
User-Agent: LANCOM PBX
Authorization: Digest username="jhilgers",realm="etc.tario.ru",algorithm=MD5,uri="sip:sipnet.ru",nonce="FF95E4DEB4B9D991FBD2",response="d9113c448e2e8ec1a4602cfcb8bc6ed0"
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:22,730
Receiving Datagram with length 480 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>;tag=2B29B9AB28E44317
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="FF95E4DEB4B9D991FBD2",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:23,790
Receiving Datagram with length 378 from 212.53.35.219:5060:
SIP/2.0 401 incorrect password or account name
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-b33aa419-b425d12c;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: "1678128" <sip:1678128@sipnet.ru>;tag=AC7EE83FFBCCF9D7
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:26,730
Receiving Datagram with length 480 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>;tag=2B29B9AB28E44317
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="FF95E4DEB4B9D991FBD2",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:30,720
Receiving Datagram with length 480 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>;tag=2B29B9AB28E44317
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="FF95E4DEB4B9D991FBD2",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:34,730
Receiving Datagram with length 480 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>;tag=2B29B9AB28E44317
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="FF95E4DEB4B9D991FBD2",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[Callmanager] 2006/02/10 19:48:36,510

Disconnect: 78122671623@sipnet.ru Cause:102

[SIP-Packet] 2006/02/10 19:48:38,730
Receiving Datagram with length 480 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>;tag=2B29B9AB28E44317
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="FF95E4DEB4B9D991FBD2",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:40,440
Sending Datagram with length 383 to 212.53.35.219:5060:
ACK sip:78122671623@sipnet.ru:5060 SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-b33aa419-b425d12c
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 2 ACK
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:42,730
Receiving Datagram with length 480 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>;tag=2B29B9AB28E44317
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="FF95E4DEB4B9D991FBD2",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:46,720
Receiving Datagram with length 480 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>;tag=2B29B9AB28E44317
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="FF95E4DEB4B9D991FBD2",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:48:50,730
Receiving Datagram with length 480 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-a1799aa7-bd044e73;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=3900006495-2575446799
To: <sip:78122671623@sipnet.ru>;tag=2B29B9AB28E44317
Call-ID: 194758399@00:a0:57:11:a5:43
CSeq: 1 INVITE
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="FF95E4DEB4B9D991FBD2",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:49:08,510
Sending Datagram with length 421 to 212.53.35.219:5060:
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-19362499-e123916c
From: "1678128" <sip:1678128@sipnet.ru>;tag=1691914852-845957426
To: "1678128" <sip:1678128@sipnet.ru>
Call-ID: 3383829704@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:1678128@84.187.234.252:39395>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 2006/02/10 19:49:08,660
Receiving Datagram with length 488 from 212.53.35.219:5060:
SIP/2.0 401 Authentication required
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-19362499-e123916c;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=1691914852-845957426
To: "1678128" <sip:1678128@sipnet.ru>;tag=38D4F9E27BC76833
Call-ID: 3383829704@00:a0:57:11:a5:43
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="etc.tario.ru",nonce="C25564D1289F5A77E45E",opaque="opaqueData",qop="auth",algorithm=MD5
Server: CommuniGatePro/5.0.8
Content-Length: 0



[SIP-Packet] 2006/02/10 19:49:08,660
Sending Datagram with length 592 to 212.53.35.219:5060:
REGISTER sip:sipnet.ru SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-44e50ee2-22728771
From: "1678128" <sip:1678128@sipnet.ru>;tag=1691914852-845957426
To: "1678128" <sip:1678128@sipnet.ru>
Call-ID: 3383829704@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:1678128@84.187.234.252:39395>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="jhilgers",realm="etc.tario.ru",algorithm=MD5,uri="sip:sipnet.ru",nonce="C25564D1289F5A77E45E",response="9e5d5e8f2de841a87b85e90d25ed0285"
Content-Length: 0



[SIP-Packet] 2006/02/10 19:49:09,480
Receiving Datagram with length 631 from 212.53.35.219:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.187.234.252:39395;branch=z9hG4bK-44e50ee2-22728771;received=84.187.234.252
From: "1678128" <sip:1678128@sipnet.ru>;tag=1691914852-845957426
To: "1678128" <sip:1678128@sipnet.ru>;tag=E0E5F8F94FFCF183
Call-ID: 3383829704@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Expires: 240
Contact: <sip:1678128@84.187.234.252:39395>;expires=240
Contact: <sip:1678128@217.250.174.170:39395>;expires=118
Event: registration
Date: Fri, 10 Feb 2006 18:49:27 GMT
Allow: PUBLISH,SUBSCRIBE
Allow-Events: presence,message-summary,reg,keep-alive
Supported: path
Server: CommuniGatePro/5.0.8
Content-Length: 0


SO jetzt hier zum Vergleich das Trace von der Fritzbox:

# Feb 10 19:18:35 voipd[598]: <<<udp Status: 403 Zugriff nicht erlaubt
Feb 10 19:18:35 voipd[598]: SUBSCRIBED: message-summary sip:032226001272@tel.t-online.de 3.403
Feb 10 19:18:41 voipd[598]: incoming(5:appl=4 plci=0x705 ncci=0x0 incoming): 10 78122671623 <- 1
Feb 10 19:18:41 voipd[598]: telapp_incoming - running (voip=0)
Feb 10 19:18:41 voipd[598]: 0: connected vcc 1/32/PPPoE/32 stay online 1
Feb 10 19:18:41 voipd[598]: 0: ip 84.187.164.122/217.0.116.9 mtu 1492 dns 217.237.150.97/217.237.149.161
Feb 10 19:18:41 voipd[598]: allowed bandwidth 144000 for sip:78122671623@sipnet.ru
Feb 10 19:18:41 voipd[598]: jhilgers@sipnet.ru: bandwidth left 144000
Feb 10 19:18:41 voipd[598]: >>>udp Request: INVITE sip:78122671623@sipnet.ru
Feb 10 19:18:41 voipd[598]: <<<udp Status: 100 Trying
Feb 10 19:18:41 voipd[598]: <<<udp Status: 401 Authentication required
Feb 10 19:18:41 voipd[598]: >>>udp Request: ACK sip:78122671623@sipnet.ru
Feb 10 19:18:41 voipd[598]: allowed bandwidth 144000 for sip:78122671623@sipnet.ru
Feb 10 19:18:41 voipd[598]: jhilgers@sipnet.ru: bandwidth left 144000
Feb 10 19:18:41 voipd[598]: >>>udp Request: INVITE sip:78122671623@sipnet.ru
Feb 10 19:18:41 voipd[598]: <<<udp Status: 100 Trying
Feb 10 19:18:42 voipd[598]: <<<udp Status: 180 Ringing
Feb 10 19:18:42 voipd[598]: allowed bandwidth 144000 for sip:78122671623@sipnet.ru
Feb 10 19:18:42 voipd[598]: jhilgers@sipnet.ru: bandwidth left 144000
Feb 10 19:18:42 voipd[598]: audio: 8 (8 PCMA/8000)
Feb 10 19:18:42 voipd[598]: audio: 8 (8 PCMA/8000) => (8 (8 PCMA/8000))
Feb 10 19:18:42 voipd[598]: 195.131.91.6 18612 - 7078 audio 8(PCMA)
Feb 10 19:18:42 voipd[598]: capienabledrop 1
Feb 10 19:18:42 voipd[598]: Codec PCMA (8) - audio 98933 hold=none (none) (by local)
Feb 10 19:18:42 voipd[598]: rtp_start_session(image): no session definition
Feb 10 19:18:42 voipd[598]: rtp_start_session(video): no session definition
Feb 10 19:18:42 voipd[598]: bridgelimit: nConnections=1
Feb 10 19:18:42 voipd[598]: number of bridge interfaces 1
Feb 10 19:18:42 voipd[598]: found bridge lan with tiwlan0
Feb 10 19:18:42 voipd[598]: bridge lan set to max 30 packets/100ms
Feb 10 19:18:42 voipd[598]: plci_connected(appl=4 plci=0x705 ncci=0x0 incoming)
Feb 10 19:18:42 voipd[598]: capiconn_send: failed 1
Feb 10 19:18:42 voipd[598]: connected(appl=4 plci=0x705 ncci=0x10705 incoming) NCPIlen=0
Feb 10 19:18:47 voipd[598]: <<<udp Status: 183 Session Progress
Feb 10 19:18:47 voipd[598]: allowed bandwidth 144000 for sip:78122671623@sipnet.ru
Feb 10 19:18:47 voipd[598]: jhilgers@sipnet.ru: bandwidth left 144000
Feb 10 19:18:47 voipd[598]: audio: 8 (8 PCMA/8000)
Feb 10 19:18:47 voipd[598]: audio: 8 (8 PCMA/8000) => (8 (8 PCMA/8000))
Feb 10 19:18:47 voipd[598]: Codec PCMA (8) - audio 98933 hold=none (none) (by local)
Feb 10 19:18:47 voipd[598]: rtp_start_session(image): no session definition
Feb 10 19:18:47 voipd[598]: rtp_start_session(video): no session definition
Feb 10 19:19:03 voipd[598]: <<<udp Request: OPTIONS sip:801293@84.187.164.122;uniq=956C586883132296046ED82607D1A
Feb 10 19:19:03 voipd[598]: >>>udp Status: 200 OK
Feb 10 19:19:04 voipd[598]: <<<udp Status: 200 OK
Feb 10 19:19:04 voipd[598]: allowed bandwidth 144000 for sip:78122671623@sipnet.ru
Feb 10 19:19:04 voipd[598]: jhilgers@sipnet.ru: bandwidth left 144000
Feb 10 19:19:04 voipd[598]: audio: 8 (8 PCMA/8000)
Feb 10 19:19:04 voipd[598]: audio: 8 (8 PCMA/8000) => (8 (8 PCMA/8000))
Feb 10 19:19:04 voipd[598]: Codec PCMA (8) - audio 98933 hold=none (none) (by local)
Feb 10 19:19:04 voipd[598]: rtp_start_session(image): no session definition
Feb 10 19:19:04 voipd[598]: rtp_start_session(video): no session definition
Feb 10 19:19:04 voipd[598]: call to sip:78122671623@sipnet.ru established
Feb 10 19:19:04 voipd[598]: >>>udp Request: ACK sip:proc-389534720@212.53.35.244

Die anderen Trace schicke ich gleich.

Gruss
Jochen
Nach oben
jhilgers
Beiträge: 175
Registriert: 02 Mär 2005, 14:39
Wohnort: Aachen

FWD Logfiles

Beitrag von jhilgers »

Hier ist der Trace, wenn mich jemand über den Provide FWD anruft. Danach passiert nichts mehr. Ich höre nur besetzt.

> trace + call sip @ fwd
Callmanager ON @ fwd
SIP-Packet ON @ fwd

jhilgers@Lancom1722:/
>
[SIP-Packet] 2006/02/10 19:57:18,510
Sending Datagram with length 414 to 69.90.155.70:5060:
REGISTER sip:fwd.pulver.com SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:35065;branch=z9hG4bK-55f19e41-c7404c00
From: <sip:618165@fwd.pulver.com>;tag=2360835909-2883796098
To: <sip:618165@fwd.pulver.com>
Call-ID: 3256875211@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:618165@84.187.234.252:35065>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 2006/02/10 19:57:18,680
Receiving Datagram with length 463 from 69.90.155.70:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.187.234.252:35065;branch=z9hG4bK-55f19e41-c7404c00
From: <sip:618165@fwd.pulver.com>;tag=2360835909-2883796098
To: <sip:618165@fwd.pulver.com>;tag=cb2000b247d89723001a836145f3b053.c65b
Call-ID: 3256875211@00:a0:57:11:a5:43
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="fwd.pulver.com", nonce="43ece864795ca0037b8acac6370774fc3f0eae89"
Server: Sip EXpress router (0.8.14-6 (i386/linux))
Content-Length: 0



[SIP-Packet] 2006/02/10 19:57:18,680
Sending Datagram with length 610 to 69.90.155.70:5060:
REGISTER sip:fwd.pulver.com SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:35065;branch=z9hG4bK-031d0130-018e8098
From: <sip:618165@fwd.pulver.com>;tag=2360835909-2883796098
To: <sip:618165@fwd.pulver.com>
Call-ID: 3256875211@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:618165@84.187.234.252:35065>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="618165",realm="fwd.pulver.com",algorithm=MD5,uri="sip:fwd.pulver.com",nonce="43ece864795ca0037b8acac6370774fc3f0eae89",response="6a61bde48f7cc76610db80d8ddfafb54"
Content-Length: 0



[SIP-Packet] 2006/02/10 19:57:18,890
Receiving Datagram with length 417 from 69.90.155.70:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.187.234.252:35065;branch=z9hG4bK-031d0130-018e8098
From: <sip:618165@fwd.pulver.com>;tag=2360835909-2883796098
To: <sip:618165@fwd.pulver.com>;tag=cb2000b247d89723001a836145f3b053.905c
Call-ID: 3256875211@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Contact: <sip:618165@84.187.234.252:35065>;q=0.00;expires=240
Server: Sip EXpress router (0.8.14-6 (i386/linux))
Content-Length: 0




jhilgers@Lancom1722:/
>

jhilgers@Lancom1722:/
>

jhilgers@Lancom1722:/
>
[Callmanager] 2006/02/10 19:58:29,750
From: 82671623@213.170.111.50 Line: 'FWD'
To : 17@213.170.92.166 <Number is complete>
Info: Parse call routing table for active entries
Info: Search in the local user database
Info: User '17@213.170.92.166' not found
Info: Ignore domain
==> From: 82671623@213.170.111.50 Line: 'FWD'
To : 17@intern Line: 'USER.ISDN'
InitiateCall: 17@intern Line: 'USER.ISDN'

[SIP-Packet] 2006/02/10 19:58:29,770
Sending Datagram with length 779 to 69.90.155.70:5060:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 69.90.155.70;received=69.90.155.70:5060;branch=z9hG4bK1366.af975fa5.0
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK1366.a3372283.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=d8d83315fc09a779a6efce7f9b1914d1.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=1471febded0e24d464c4eb4d55c105d9.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ff03580060ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ff01580060ffff10ff00000fff3bff2a
To: <sip:618165@fwd.pulver.com>;tag=3879506807-2653342363
Call-ID: 3e00580060e2ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 2006/02/10 19:58:29,970
Sending Datagram with length 780 to 69.90.155.70:5060:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 69.90.155.70;received=69.90.155.70:5060;branch=z9hG4bK1366.af975fa5.0
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK1366.a3372283.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=d8d83315fc09a779a6efce7f9b1914d1.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=1471febded0e24d464c4eb4d55c105d9.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ff03580060ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ff01580060ffff10ff00000fff3bff2a
To: <sip:618165@fwd.pulver.com>;tag=3879506807-2653342363
Call-ID: 3e00580060e2ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 2006/02/10 19:58:33,680
Sending Datagram with length 994 to 69.90.155.70:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 69.90.155.70;received=69.90.155.70:5060;branch=z9hG4bK1366.af975fa5.0
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK1366.a3372283.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=d8d83315fc09a779a6efce7f9b1914d1.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=1471febded0e24d464c4eb4d55c105d9.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ff03580060ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ff01580060ffff10ff00000fff3bff2a
To: <sip:618165@fwd.pulver.com>;tag=3879506807-2653342363
Call-ID: 3e00580060e2ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:618165@84.187.234.252:35065>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37652 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 19:58:35,510
Sending Datagram with length 994 to 69.90.155.70:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 69.90.155.70;received=69.90.155.70:5060;branch=z9hG4bK1366.af975fa5.0
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK1366.a3372283.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=d8d83315fc09a779a6efce7f9b1914d1.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=1471febded0e24d464c4eb4d55c105d9.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ff03580060ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ff01580060ffff10ff00000fff3bff2a
To: <sip:618165@fwd.pulver.com>;tag=3879506807-2653342363
Call-ID: 3e00580060e2ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:618165@84.187.234.252:35065>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37652 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 19:58:37,510
Sending Datagram with length 994 to 69.90.155.70:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 69.90.155.70;received=69.90.155.70:5060;branch=z9hG4bK1366.af975fa5.0
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK1366.a3372283.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=d8d83315fc09a779a6efce7f9b1914d1.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=1471febded0e24d464c4eb4d55c105d9.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ff03580060ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ff01580060ffff10ff00000fff3bff2a
To: <sip:618165@fwd.pulver.com>;tag=3879506807-2653342363
Call-ID: 3e00580060e2ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:618165@84.187.234.252:35065>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37652 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 19:58:41,510
Sending Datagram with length 994 to 69.90.155.70:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 69.90.155.70;received=69.90.155.70:5060;branch=z9hG4bK1366.af975fa5.0
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK1366.a3372283.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=d8d83315fc09a779a6efce7f9b1914d1.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=1471febded0e24d464c4eb4d55c105d9.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ff03580060ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ff01580060ffff10ff00000fff3bff2a
To: <sip:618165@fwd.pulver.com>;tag=3879506807-2653342363
Call-ID: 3e00580060e2ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:618165@84.187.234.252:35065>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37652 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 19:58:45,510
Sending Datagram with length 994 to 69.90.155.70:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 69.90.155.70;received=69.90.155.70:5060;branch=z9hG4bK1366.af975fa5.0
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK1366.a3372283.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=d8d83315fc09a779a6efce7f9b1914d1.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=1471febded0e24d464c4eb4d55c105d9.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ff03580060ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ff01580060ffff10ff00000fff3bff2a
To: <sip:618165@fwd.pulver.com>;tag=3879506807-2653342363
Call-ID: 3e00580060e2ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:618165@84.187.234.252:35065>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37652 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 19:58:49,510
Sending Datagram with length 994 to 69.90.155.70:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 69.90.155.70;received=69.90.155.70:5060;branch=z9hG4bK1366.af975fa5.0
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK1366.a3372283.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=d8d83315fc09a779a6efce7f9b1914d1.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=1471febded0e24d464c4eb4d55c105d9.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ff03580060ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=ff01580060ffff10ff00000fff3bff2a
To: <sip:618165@fwd.pulver.com>;tag=3879506807-2653342363
Call-ID: 3e00580060e2ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:618165@84.187.234.252:35065>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37652 RTP/AVP 8
a=rtpmap:8 PCMA/8000
Nach oben
jhilgers
Beiträge: 175
Registriert: 02 Mär 2005, 14:39
Wohnort: Aachen

SIPGATE Tracefile

Beitrag von jhilgers »

So hier kommt nun der gleiche Anruf über SIPGATE rein. Das Verhalten unterscheidet sich nur, das ich selber auflegen muss. Im Telefon ist nur Stille:

> trace + call sip @ sipgate
Callmanager ON @ sipgate
SIP-Packet ON @ sipgate

jhilgers@Lancom1722:/
>
[SIP-Packet] 2006/02/10 20:05:09,510
Sending Datagram with length 402 to 217.10.79.9:5060:
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:41076;branch=z9hG4bK-9ba70481-a06b0160
From: <sip:8001960@sipgate.de>;tag=51321031-3963555651
To: <sip:8001960@sipgate.de>
Call-ID: 102642062@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:8001960@84.187.234.252:41076>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 2006/02/10 20:05:09,590
Receiving Datagram with length 586 from 217.10.79.9:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.187.234.252:41076;branch=z9hG4bK-9ba70481-a06b0160
From: <sip:8001960@sipgate.de>;tag=51321031-3963555651
To: <sip:8001960@sipgate.de>;tag=b11cb9bb270104b49a99a995b8c68544.7b7a
Call-ID: 102642062@00:a0:57:11:a5:43
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sipgate.de", nonce="43ece526306c99b4c69e9af181b330e0a0bcff82"
Server: sipgate ser
Content-Length: 0
Warning: 392 217.10.79.9:5060 "Noisy feedback tells: pid=25001 req_src_ip=84.187.234.252 req_src_port=41076 in_uri=sip:sipgate.de out_uri=sip:sipgate.de via_cnt==1"



[SIP-Packet] 2006/02/10 20:05:09,600
Sending Datagram with length 591 to 217.10.79.9:5060:
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:41076;branch=z9hG4bK-503580b0-281ac058
From: <sip:8001960@sipgate.de>;tag=51321031-3963555651
To: <sip:8001960@sipgate.de>
Call-ID: 102642062@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:8001960@84.187.234.252:41076>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="8001960",realm="sipgate.de",algorithm=MD5,uri="sip:sipgate.de",nonce="43ece526306c99b4c69e9af181b330e0a0bcff82",response="0ef83d03e4817415995de918633ff2a1"
Content-Length: 0



[SIP-Packet] 2006/02/10 20:05:09,700
Receiving Datagram with length 545 from 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.187.234.252:41076;branch=z9hG4bK-503580b0-281ac058
From: <sip:8001960@sipgate.de>;tag=51321031-3963555651
To: <sip:8001960@sipgate.de>;tag=b11cb9bb270104b49a99a995b8c68544.0e8d
Call-ID: 102642062@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Contact: <sip:8001960@84.187.234.252:41076>;q=0.00;expires=240
Server: sipgate ser
Content-Length: 0
Warning: 392 217.10.79.9:5060 "Noisy feedback tells: pid=25001 req_src_ip=84.187.234.252 req_src_port=41076 in_uri=sip:sipgate.de out_uri=sip:sipgate.de via_cnt==1"



[Callmanager] 2006/02/10 20:05:25,760
From: 82671623@213.170.111.50 Line: 'SIPGATE'
To : 10@213.170.92.166 <Number is complete>
Info: Parse call routing table for active entries
Info: Search in the local user database
Info: User '10@213.170.92.166' not found
Info: Ignore domain
==> From: 82671623@213.170.111.50 Line: 'SIPGATE'
To : 10@intern Line: 'USER.ISDN'
InitiateCall: 10@intern Line: 'USER.ISDN'

[SIP-Packet] 2006/02/10 20:05:25,770
Sending Datagram with length 773 to 217.10.79.9:5060:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 2006/02/10 20:05:25,980
Sending Datagram with length 774 to 217.10.79.9:5060:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 2006/02/10 20:05:30,260
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:05:31,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:05:33,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:05:37,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:05:41,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:05:45,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:05:49,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:05:53,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:05:57,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:01,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:05,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:09,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:13,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:17,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:21,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:25,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:29,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:33,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:37,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:41,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:45,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:49,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:53,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:57,510
Sending Datagram with length 989 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:82671623@213.170.111.50>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:06:59,150
Sending Datagram with length 845 to 217.10.79.9:5060:
BYE sip:82671623@213.170.111.50 SIP/2.0
Via: SIP/2.0/UDP 84.187.234.252:41076;branch=z9hG4bK-e363c019-9c09632c
Route: <SIP:8001960@217.10.79.9;ftag=3cff540000ffff10ff00000fff3bff2a;lr=on>
Route: <SIP:**00078123364291@69.90.155.68;ftag=3cff540000ffff10ff00000fff3bff2a;lr=on>
Route: <SIP:78123364291@213.170.92.166:5060;maddr=213.170.92.166>
Route: <SIP:78123364291@213.170.92.166:5043;maddr=213.170.92.166>
Route: <SIP:**00078123364291@213.170.92.166:8018;maddr=213.170.92.166>
From: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
To: <sip:8001960@sipgate.de>;tag=3cff540000ffff10ff00000fff3bff2a
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 2 BYE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Length: 0



[SIP-Packet] 2006/02/10 20:07:01,510
Sending Datagram with length 984 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:8001960@sipgate.de>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 2 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 2006/02/10 20:07:05,510
Sending Datagram with length 984 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK0e0c.678bba37.1
Via: SIP/2.0/UDP 69.90.155.68;branch=z9hG4bK0e0c.0ecc662.0
Via: SIP/2.0/UDP 213.170.92.166:8018;branch=fd0ed1993498817b80f8d966b4146c00.4
Via: SIP/2.0/UDP 213.170.92.166:5043;branch=ca4a54c6392834680d73e816075bb4d8.2
Via: SIP/2.0/UDP 213.170.92.166:5060
Via: SIP/2.0/UDP 213.170.111.50:5060;branch=z9hG4bK-ffff540000ffff10ff00000fff3bff2a
From: <sip:8001960@sipgate.de>;tag=3cff540000ffff10ff00000fff3bff2a
To: <sip:8001960@sipgate.de>;tag=1954750203-3623423069
Call-ID: e8f9540000e4ec108000000fea3bc72a@siphit.quantum.ru
CSeq: 2 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.234.252:41076>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.234.252
s=Lancom PBX
c=IN IP4 84.187.234.252
t=0 0
m=audio 37321 RTP/AVP 8
a=rtpmap:8 PCMA/8000
Nach oben
jhilgers
Beiträge: 175
Registriert: 02 Mär 2005, 14:39
Wohnort: Aachen

Anruf von GMX zu SIPGATE

Beitrag von jhilgers »

Hallo nochmals,

damit es nicht zu langweilig wird :-), habe ich mich jetzt mal selber angerufen. Also von GMX zu SIPGATE und habe das ganze mal mitgeschnitten.

Bevor ich jetzt die Logfiles mitschicke, hier noch ein paar Anmerkungen. Wenn ich die Nummer gewählt habe, habe ich dreimal Tuten gehört (so als würde es beim anderen Klingeln), jedoch hat das Telefon nicht geklingelt. Erst nach dem dritten Tuten, fing es dann an zu klingeln. Ich hebe den Hörer ab. Die Verbindung scheint dann zu stehen. Ich höre mich :-) Doch direkt nach 1 oder 2 Sekunden, wird die Verbindung getrennt. Das höre ich am Besetztton am angerufenen Telefon. Das ganze ist Reproduzierbar.

Hier also die Logs.
GMX:
[Callmanager] 1900/01/01 00:25:28,740
From: 10@intern Line: 'USER.ISDN'
To : 021158001960@intern
Info: Parse call routing table for active entries
RESTART line ==> reparse!!
To : 0021158001960@intern
Info: Parse call routing table for active entries
==> From: 10@intern Line: ''
To : 021158001960@sip.gmx.net Line: 'GMX'
InitiateCall: 021158001960@sip.gmx.net Line: 'GMX'

[SIP-Packet] 1900/01/01 00:25:34,400
Sending Datagram with length 766 to 212.227.15.197:5060:
INVITE sip:021158001960@sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-42eff0d1-cccf7b48
From: "Privat" <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:492405418430@84.187.193.236:37321>
Content-Type: application/sdp
Content-Length: 286

v=0
o=Lancom 12345 6789 IN IP4 84.187.193.236
s=Lancom PBX
c=IN IP4 84.187.193.236
t=0 0
m=audio 44895 RTP/AVP 8 0 106 2 104 103
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:106 G726-40/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:104 G726-24/8000
a=rtpmap:103 G726-16/8000


[SIP-Packet] 1900/01/01 00:25:34,500
Receiving Datagram with length 478 from 212.227.15.197:5060:
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-42eff0d1-cccf7b48
From: "Privat" <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>;tag=329cfeaa6ded039da25ff8cbb8668bd2.7681
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 1 INVITE
Proxy-Authenticate: Digest realm="sip-gmx.net", nonce="43ee5da5f2aa3dadc9cb6441378a6a04f7c288e8"
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:34,500
Sending Datagram with length 396 to 212.227.15.197:5060:
ACK sip:021158001960@sip.gmx.net:5060 SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-42eff0d1-cccf7b48
From: "Privat" <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 1 ACK
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:34,500
Sending Datagram with length 981 to 212.227.15.197:5060:
INVITE sip:021158001960@sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-3333ded2-1999ef69
From: "Privat" <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 2 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Proxy-Authorization: Digest username="492405418430",realm="sip-gmx.net",nonce="43ee5da5f2aa3dadc9cb6441378a6a04f7c288e8",uri="sip:021158001960@sip.gmx.net",response="c98c6b83b01927102948fa35992b794b",algorithm=md5
Contact: <sip:492405418430@84.187.193.236:37321>
Content-Type: application/sdp
Content-Length: 286

v=0
o=Lancom 12345 6789 IN IP4 84.187.193.236
s=Lancom PBX
c=IN IP4 84.187.193.236
t=0 0
m=audio 44895 RTP/AVP 8 0 106 2 104 103
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:106 G726-40/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:104 G726-24/8000
a=rtpmap:103 G726-16/8000


[SIP-Packet] 1900/01/01 00:25:34,640
Receiving Datagram with length 347 from 212.227.15.197:5060:
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-3333ded2-1999ef69
From: "Privat" <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 2 INVITE
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:38,600
Receiving Datagram with length 712 from 212.227.15.197:5060:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-3333ded2-1999ef69
From: <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>;tag=1210145708
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 2 INVITE
Contact: <sip:4921158001960@sipgw01.bmcag.com:5060>
Content-Type: application/sdp
Content-Length: 312
X-Route-Info: PSTN

v=0
o=- 125338 1 IN IP4 62.206.224.138
s=Cisco SDP 0
c=IN IP4 62.206.224.138
t=0 0
m=audio 18378 RTP/AVP 0 110
a=rtpmap:110 X-NSE/8000
a=fmtp:110 192-194,200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 110
a=X-cpar: a=rtpmap:110 X-NSE/8000
a=X-cpar: a=fmtp:110 192-194,200-202
a=X-cap: 2 image udptl t38


[SIP-Packet] 1900/01/01 00:25:50,040
Receiving Datagram with length 358 from 212.227.15.197:5060:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-3333ded2-1999ef69
From: <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>;tag=1210145708
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 2 INVITE
Contact: <sip:4921158001960@sipgw01.bmcag.com:5060>
Content-Length: 0
X-Route-Info: PSTN



[SIP-Packet] 1900/01/01 00:25:55,460
Receiving Datagram with length 838 from 212.227.15.197:5060:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-3333ded2-1999ef69
From: <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>;tag=1210145708
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 2 INVITE
Contact: <sip:4921158001960@sipgw01.bmcag.com:5060>
Record-Route: <sip:212.227.15.198;ftag=3503211781-2246042018;lr=on>
Allow: INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDATE
Content-Type: application/sdp
Content-Length: 312
X-Route-Info: PSTN

v=0
o=- 125338 1 IN IP4 62.206.224.138
s=Cisco SDP 0
c=IN IP4 62.206.224.138
t=0 0
m=audio 18378 RTP/AVP 0 110
a=rtpmap:110 X-NSE/8000
a=fmtp:110 192-194,200-202
a=X-sqn:0
a=X-cap: 1 audio RTP/AVP 110
a=X-cpar: a=rtpmap:110 X-NSE/8000
a=X-cpar: a=fmtp:110 192-194,200-202
a=X-cap: 2 image udptl t38


[SIP-Packet] 1900/01/01 00:25:55,480
Sending Datagram with length 531 to 212.227.15.197:5060:
ACK sip:4921158001960@sipgw01.bmcag.com:5060 SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-42451b4f-cc9a0e87
Route: <SIP:212.227.15.198;ftag=3503211781-2246042018;lr=on>
From: "Privat" <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>;tag=1210145708
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 2 ACK
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:4921158001960@84.187.193.236:37321>
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:55,480
Sending Datagram with length 480 to 212.227.15.197:5060:
BYE sip:4921158001960@sipgw01.bmcag.com:5060 SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-42451b4f-cc9a0e87
Route: <SIP:212.227.15.198;ftag=3503211781-2246042018;lr=on>
From: "Privat" <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>;tag=1210145708
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 2 BYE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:55,790
Receiving Datagram with length 285 from 212.227.15.197:5060:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-42451b4f-cc9a0e87
From: "Privat" <sip:492405418430@sip.gmx.net>;tag=3503211781-2246042018
To: <sip:021158001960@sip.gmx.net>;tag=1210145708
Call-ID: 2062322763@00:a0:57:11:a5:43
CSeq: 2 BYE
Content-Length: 0



[SIP-Packet] 1900/01/01 00:26:26,400
Sending Datagram with length 423 to 212.227.15.197:5060:
REGISTER sip:sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-29017d2a-1480be95
From: <sip:492405418430@sip.gmx.net>;tag=2751853736-1375926868
To: <sip:492405418430@sip.gmx.net>
Call-ID: 2474307345@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:492405418430@84.187.193.236:37321>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 1900/01/01 00:26:26,510
Receiving Datagram with length 452 from 212.227.15.197:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-29017d2a-1480be95
From: <sip:492405418430@sip.gmx.net>;tag=2751853736-1375926868
To: <sip:492405418430@sip.gmx.net>;tag=329cfeaa6ded039da25ff8cbb8668bd2.c72b
Call-ID: 2474307345@00:a0:57:11:a5:43
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip-gmx.net", nonce="43ee5dd95090149a3e7d56815f5f52569763cba8"
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 1900/01/01 00:26:26,510
Sending Datagram with length 619 to 212.227.15.197:5060:
REGISTER sip:sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-8071e775-ad80709a
From: <sip:492405418430@sip.gmx.net>;tag=2751853736-1375926868
To: <sip:492405418430@sip.gmx.net>
Call-ID: 2474307345@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:492405418430@84.187.193.236:37321>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="492405418430",realm="sip-gmx.net",algorithm=MD5,uri="sip:sip.gmx.net",nonce="43ee5dd95090149a3e7d56815f5f52569763cba8",response="b18640abf29d2048c46db8e0a07e9098"
Content-Length: 0



[SIP-Packet] 1900/01/01 00:26:26,720
Receiving Datagram with length 409 from 212.227.15.197:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-8071e775-ad80709a
From: <sip:492405418430@sip.gmx.net>;tag=2751853736-1375926868
To: <sip:492405418430@sip.gmx.net>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-9fd8
Call-ID: 2474307345@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Contact: <sip:492405418430@84.187.193.236:37321>;expires=3532
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 1900/01/01 00:28:26,400
Sending Datagram with length 423 to 212.227.15.197:5060:
REGISTER sip:sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-f3ad5bc4-79d6ade2
From: <sip:492405418430@sip.gmx.net>;tag=2018993042-1009496521
To: <sip:492405418430@sip.gmx.net>
Call-ID: 4037986084@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:492405418430@84.187.193.236:37321>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 1900/01/01 00:28:26,510
Receiving Datagram with length 452 from 212.227.15.197:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-f3ad5bc4-79d6ade2
From: <sip:492405418430@sip.gmx.net>;tag=2018993042-1009496521
To: <sip:492405418430@sip.gmx.net>;tag=329cfeaa6ded039da25ff8cbb8668bd2.8df3
Call-ID: 4037986084@00:a0:57:11:a5:43
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip-gmx.net", nonce="43ee5e513dacc357b157371a742dd8091d1e313b"
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 1900/01/01 00:28:26,510
Sending Datagram with length 619 to 212.227.15.197:5060:
REGISTER sip:sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-4e7d55f9-ca8629dc
From: <sip:492405418430@sip.gmx.net>;tag=2018993042-1009496521
To: <sip:492405418430@sip.gmx.net>
Call-ID: 4037986084@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:492405418430@84.187.193.236:37321>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="492405418430",realm="sip-gmx.net",algorithm=MD5,uri="sip:sip.gmx.net",nonce="43ee5e513dacc357b157371a742dd8091d1e313b",response="bbb273b9fa986ad49717f279066b82b6"
Content-Length: 0



[SIP-Packet] 1900/01/01 00:28:26,640
Receiving Datagram with length 409 from 212.227.15.197:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-4e7d55f9-ca8629dc
From: <sip:492405418430@sip.gmx.net>;tag=2018993042-1009496521
To: <sip:492405418430@sip.gmx.net>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-83ff
Call-ID: 4037986084@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Contact: <sip:492405418430@84.187.193.236:37321>;expires=3060
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 1900/01/01 00:30:26,400
Sending Datagram with length 423 to 212.227.15.197:5060:
REGISTER sip:sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-41025a13-cd39ae29
From: <sip:492405418430@sip.gmx.net>;tag=3749211661-2181346342
To: <sip:492405418430@sip.gmx.net>
Call-ID: 1703008859@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:492405418430@84.187.193.236:37321>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 1900/01/01 00:30:26,510
Receiving Datagram with length 452 from 212.227.15.197:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-41025a13-cd39ae29
From: <sip:492405418430@sip.gmx.net>;tag=3749211661-2181346342
To: <sip:492405418430@sip.gmx.net>;tag=329cfeaa6ded039da25ff8cbb8668bd2.b16b
Call-ID: 1703008859@00:a0:57:11:a5:43
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip-gmx.net", nonce="43ee5ec9da390120f4f8d068e9abfb020f38677c"
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0



[SIP-Packet] 1900/01/01 00:30:26,510
Sending Datagram with length 619 to 212.227.15.197:5060:
REGISTER sip:sip.gmx.net SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-427fa1c2-213fd0e1
From: <sip:492405418430@sip.gmx.net>;tag=3749211661-2181346342
To: <sip:492405418430@sip.gmx.net>
Call-ID: 1703008859@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:492405418430@84.187.193.236:37321>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="492405418430",realm="sip-gmx.net",algorithm=MD5,uri="sip:sip.gmx.net",nonce="43ee5ec9da390120f4f8d068e9abfb020f38677c",response="866a7928fa8e08c16fc96219f4c8af3f"
Content-Length: 0



[SIP-Packet] 1900/01/01 00:30:26,640
Receiving Datagram with length 409 from 212.227.15.197:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.187.193.236:37321;branch=z9hG4bK-427fa1c2-213fd0e1
From: <sip:492405418430@sip.gmx.net>;tag=3749211661-2181346342
To: <sip:492405418430@sip.gmx.net>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-ce6a
Call-ID: 1703008859@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Contact: <sip:492405418430@84.187.193.236:37321>;expires=3192
Server: OpenSer (0.9.5 (i386/linux))
Content-Length: 0


Und jetzt noch SIPGATE (als Angerufene Gegenstelle)
[SIP-Packet] 1900/01/01 00:25:49,010
Receiving Datagram with length 1176 from 217.10.79.9:5060:
INVITE sip:8001960@84.187.193.236:38518 SIP/2.0
Record-Route: <sip:8001960@217.10.79.9;ftag=as238ecdc2;lr=on>
Max-Forwards: 9
Record-Route: <sip:4921158001960@217.10.79.8;ftag=as238ecdc2;lr=on>
Via: SIP/2.0/UDP 217.10.79.9;branch=z9hG4bK95ee.6c48b434.1
Via: SIP/2.0/UDP 217.10.79.8;branch=z9hG4bK95ee.fe4d2c25.0
Via: SIP/2.0/UDP 217.10.67.5:5060;branch=z9hG4bK5e0f03fa
From: "02405418430" <sip:02405418430@217.10.67.5>;tag=as238ecdc2
To: <sip:4921158001960@217.10.79.8>
Contact: <sip:02405418430@217.10.67.5>
Call-ID: 2611138135c815163d258ece319b5db9@217.10.67.5
CSeq: 102 INVITE
User-Agent: sipgate asterisk
Date: Sat, 11 Feb 2006 21:52:00 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Content-Type: application/sdp
Content-Length: 413

v=0
o=root 24160 24160 IN IP4 217.10.67.5
s=session
c=IN IP4 217.10.67.5
t=0 0
m=audio 17212 RTP/AVP 8 0 3 97 18 111 4 5 110 7 10
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=rtpmap:18 G729/8000
a=rtpmap:111 G726-32/8000
a=rtpmap:4 G723/8000
a=rtpmap:5 DVI4/8000
a=rtpmap:110 speex/8000
a=rtpmap:7 LPC/8000
a=rtpmap:10 L16/8000
a=silenceSupp:off - - - -


[Callmanager] 1900/01/01 00:25:49,020
From: 02405418430@217.10.67.5 Line: 'SIPGATE'
To : 10@217.10.79.8 <Number is complete>
Info: Parse call routing table for active entries
Info: Search in the local user database
Info: User '10@217.10.79.8' not found
Info: Ignore domain
==> From: 02405418430@217.10.67.5 Line: 'SIPGATE'
To : 10@intern Line: 'USER.ISDN'
InitiateCall: 10@intern Line: 'USER.ISDN'

[SIP-Packet] 1900/01/01 00:25:49,040
Sending Datagram with length 534 to 217.10.79.9:5060:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK95ee.6c48b434.1
Via: SIP/2.0/UDP 217.10.79.8;branch=z9hG4bK95ee.fe4d2c25.0
Via: SIP/2.0/UDP 217.10.67.5:5060;branch=z9hG4bK5e0f03fa
From: "02405418430" <sip:02405418430@217.10.67.5>;tag=as238ecdc2
To: <sip:8001960@sipgate.de>;tag=631129261-4286030198
Call-ID: 2611138135c815163d258ece319b5db9@217.10.67.5
CSeq: 102 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:49,260
Sending Datagram with length 535 to 217.10.79.9:5060:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK95ee.6c48b434.1
Via: SIP/2.0/UDP 217.10.79.8;branch=z9hG4bK95ee.fe4d2c25.0
Via: SIP/2.0/UDP 217.10.67.5:5060;branch=z9hG4bK5e0f03fa
From: "02405418430" <sip:02405418430@217.10.67.5>;tag=as238ecdc2
To: <sip:8001960@sipgate.de>;tag=631129261-4286030198
Call-ID: 2611138135c815163d258ece319b5db9@217.10.67.5
CSeq: 102 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:54,560
Sending Datagram with length 750 to 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.10.79.9;received=217.10.79.9:5060;branch=z9hG4bK95ee.6c48b434.1
Via: SIP/2.0/UDP 217.10.79.8;branch=z9hG4bK95ee.fe4d2c25.0
Via: SIP/2.0/UDP 217.10.67.5:5060;branch=z9hG4bK5e0f03fa
From: "02405418430" <sip:02405418430@217.10.67.5>;tag=as238ecdc2
To: <sip:8001960@sipgate.de>;tag=631129261-4286030198
Call-ID: 2611138135c815163d258ece319b5db9@217.10.67.5
CSeq: 102 INVITE
Max-Forwards: 70
User-Agent: LANCOM PBX
Server: Lancom1722
Allow: INVITE, ACK, CANCEL, BYE
Contact: <sip:8001960@84.187.193.236:38518>
Content-Type: application/sdp
Content-Length: 142

v=0
o=Lancom 12345 6789 IN IP4 84.187.193.236
s=Lancom PBX
c=IN IP4 84.187.193.236
t=0 0
m=audio 37799 RTP/AVP 8
a=rtpmap:8 PCMA/8000


[SIP-Packet] 1900/01/01 00:25:54,670
Receiving Datagram with length 390 from 217.10.67.5:5060:
ACK sip:4921158001960@217.10.79.8 SIP/2.0
Via: SIP/2.0/UDP 217.10.67.5:5060;branch=z9hG4bK64b5a96d
From: "02405418430" <sip:02405418430@217.10.67.5>;tag=as238ecdc2
To: <sip:4921158001960@217.10.79.8>;tag=631129261-4286030198
Contact: <sip:02405418430@217.10.67.5>
Call-ID: 2611138135c815163d258ece319b5db9@217.10.67.5
CSeq: 102 ACK
User-Agent: sipgate asterisk
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:56,580
Receiving Datagram with length 393 from 217.10.67.5:5060:
BYE sip:8001960@84.187.193.236:38518 SIP/2.0
Via: SIP/2.0/UDP 217.10.67.5:5060;branch=z9hG4bK79ccca0b
From: "02405418430" <sip:02405418430@217.10.67.5>;tag=as238ecdc2
To: <sip:4921158001960@217.10.79.8>;tag=631129261-4286030198
Contact: <sip:02405418430@217.10.67.5>
Call-ID: 2611138135c815163d258ece319b5db9@217.10.67.5
CSeq: 103 BYE
User-Agent: sipgate asterisk
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:57,590
Receiving Datagram with length 393 from 217.10.67.5:5060:
BYE sip:8001960@84.187.193.236:38518 SIP/2.0
Via: SIP/2.0/UDP 217.10.67.5:5060;branch=z9hG4bK79ccca0b
From: "02405418430" <sip:02405418430@217.10.67.5>;tag=as238ecdc2
To: <sip:4921158001960@217.10.79.8>;tag=631129261-4286030198
Contact: <sip:02405418430@217.10.67.5>
Call-ID: 2611138135c815163d258ece319b5db9@217.10.67.5
CSeq: 103 BYE
User-Agent: sipgate asterisk
Content-Length: 0



[SIP-Packet] 1900/01/01 00:25:58,590
Receiving Datagram with length 393 from 217.10.67.5:5060:
BYE sip:8001960@84.187.193.236:38518 SIP/2.0
Via: SIP/2.0/UDP 217.10.67.5:5060;branch=z9hG4bK79ccca0b
From: "02405418430" <sip:02405418430@217.10.67.5>;tag=as238ecdc2
To: <sip:4921158001960@217.10.79.8>;tag=631129261-4286030198
Contact: <sip:02405418430@217.10.67.5>
Call-ID: 2611138135c815163d258ece319b5db9@217.10.67.5
CSeq: 103 BYE
User-Agent: sipgate asterisk
Content-Length: 0



[SIP-Packet] 1900/01/01 00:26:26,400
Sending Datagram with length 405 to 217.10.79.9:5060:
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-2078b687-fd84d863
From: <sip:8001960@sipgate.de>;tag=2179127836-1089563918
To: <sip:8001960@sipgate.de>
Call-ID: 3635720825@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:8001960@84.187.193.236:38518>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 1900/01/01 00:26:26,490
Receiving Datagram with length 589 from 217.10.79.9:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-2078b687-fd84d863
From: <sip:8001960@sipgate.de>;tag=2179127836-1089563918
To: <sip:8001960@sipgate.de>;tag=b11cb9bb270104b49a99a995b8c68544.c91c
Call-ID: 3635720825@00:a0:57:11:a5:43
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sipgate.de", nonce="43ee5dd990430a1b8c77f246a8991f637881adbf"
Server: sipgate ser
Content-Length: 0
Warning: 392 217.10.79.9:5060 "Noisy feedback tells: pid=25010 req_src_ip=84.187.193.236 req_src_port=38518 in_uri=sip:sipgate.de out_uri=sip:sipgate.de via_cnt==1"



[SIP-Packet] 1900/01/01 00:26:26,490
Sending Datagram with length 594 to 217.10.79.9:5060:
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-6c549717-db92c8ab
From: <sip:8001960@sipgate.de>;tag=2179127836-1089563918
To: <sip:8001960@sipgate.de>
Call-ID: 3635720825@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:8001960@84.187.193.236:38518>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="8001960",realm="sipgate.de",algorithm=MD5,uri="sip:sipgate.de",nonce="43ee5dd990430a1b8c77f246a8991f637881adbf",response="42cf81ec04577e5ece7bf1444d158d6a"
Content-Length: 0



[SIP-Packet] 1900/01/01 00:26:26,630
Receiving Datagram with length 548 from 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-6c549717-db92c8ab
From: <sip:8001960@sipgate.de>;tag=2179127836-1089563918
To: <sip:8001960@sipgate.de>;tag=b11cb9bb270104b49a99a995b8c68544.6303
Call-ID: 3635720825@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Contact: <sip:8001960@84.187.193.236:38518>;q=0.00;expires=240
Server: sipgate ser
Content-Length: 0
Warning: 392 217.10.79.9:5060 "Noisy feedback tells: pid=25001 req_src_ip=84.187.193.236 req_src_port=38518 in_uri=sip:sipgate.de out_uri=sip:sipgate.de via_cnt==1"



[SIP-Packet] 1900/01/01 00:28:26,400
Sending Datagram with length 403 to 217.10.79.9:5060:
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-74591012-3a2c8809
From: <sip:8001960@sipgate.de>;tag=169166345-3903987748
To: <sip:8001960@sipgate.de>
Call-ID: 338332690@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:8001960@84.187.193.236:38518>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 1900/01/01 00:28:26,490
Receiving Datagram with length 587 from 217.10.79.9:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-74591012-3a2c8809
From: <sip:8001960@sipgate.de>;tag=169166345-3903987748
To: <sip:8001960@sipgate.de>;tag=b11cb9bb270104b49a99a995b8c68544.b1e9
Call-ID: 338332690@00:a0:57:11:a5:43
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sipgate.de", nonce="43ee5e51bec94159a138bf6306af03048471be80"
Server: sipgate ser
Content-Length: 0
Warning: 392 217.10.79.9:5060 "Noisy feedback tells: pid=25005 req_src_ip=84.187.193.236 req_src_port=38518 in_uri=sip:sipgate.de out_uri=sip:sipgate.de via_cnt==1"



[SIP-Packet] 1900/01/01 00:28:26,490
Sending Datagram with length 592 to 217.10.79.9:5060:
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-e28451a5-9cfaabf2
From: <sip:8001960@sipgate.de>;tag=169166345-3903987748
To: <sip:8001960@sipgate.de>
Call-ID: 338332690@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:8001960@84.187.193.236:38518>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="8001960",realm="sipgate.de",algorithm=MD5,uri="sip:sipgate.de",nonce="43ee5e51bec94159a138bf6306af03048471be80",response="6cdcafbfad8aa9de534d66140c9f353f"
Content-Length: 0



[SIP-Packet] 1900/01/01 00:28:26,590
Receiving Datagram with length 546 from 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-e28451a5-9cfaabf2
From: <sip:8001960@sipgate.de>;tag=169166345-3903987748
To: <sip:8001960@sipgate.de>;tag=b11cb9bb270104b49a99a995b8c68544.383a
Call-ID: 338332690@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Contact: <sip:8001960@84.187.193.236:38518>;q=0.00;expires=240
Server: sipgate ser
Content-Length: 0
Warning: 392 217.10.79.9:5060 "Noisy feedback tells: pid=24999 req_src_ip=84.187.193.236 req_src_port=38518 in_uri=sip:sipgate.de out_uri=sip:sipgate.de via_cnt==1"



[SIP-Packet] 1900/01/01 00:30:26,400
Sending Datagram with length 404 to 217.10.79.9:5060:
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-4d766f2d-cb03b4b6
From: <sip:8001960@sipgate.de>;tag=4004035317-2599214682
To: <sip:8001960@sipgate.de>
Call-ID: 102790059@00:a0:57:11:a5:43
CSeq: 1 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:8001960@84.187.193.236:38518>
Expires: 240
User-Agent: LANCOM PBX
Content-Length: 0



[SIP-Packet] 1900/01/01 00:30:26,490
Receiving Datagram with length 588 from 217.10.79.9:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-4d766f2d-cb03b4b6
From: <sip:8001960@sipgate.de>;tag=4004035317-2599214682
To: <sip:8001960@sipgate.de>;tag=b11cb9bb270104b49a99a995b8c68544.6310
Call-ID: 102790059@00:a0:57:11:a5:43
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sipgate.de", nonce="43ee5ecb8ae58541d89b5966bb980c95b751c879"
Server: sipgate ser
Content-Length: 0
Warning: 392 217.10.79.9:5060 "Noisy feedback tells: pid=25006 req_src_ip=84.187.193.236 req_src_port=38518 in_uri=sip:sipgate.de out_uri=sip:sipgate.de via_cnt==1"



[SIP-Packet] 1900/01/01 00:30:26,490
Sending Datagram with length 593 to 217.10.79.9:5060:
REGISTER sip:sipgate.de SIP/2.0
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-d28f8149-84ff4384
From: <sip:8001960@sipgate.de>;tag=4004035317-2599214682
To: <sip:8001960@sipgate.de>
Call-ID: 102790059@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Allow: INVITE, ACK, CANCEL, BYE
Max-Forwards: 70
Contact: <sip:8001960@84.187.193.236:38518>
Expires: 240
User-Agent: LANCOM PBX
Authorization: Digest username="8001960",realm="sipgate.de",algorithm=MD5,uri="sip:sipgate.de",nonce="43ee5ecb8ae58541d89b5966bb980c95b751c879",response="5283a4df8699fd56192562830aecd581"
Content-Length: 0



[SIP-Packet] 1900/01/01 00:30:26,590
Receiving Datagram with length 547 from 217.10.79.9:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 84.187.193.236:38518;branch=z9hG4bK-d28f8149-84ff4384
From: <sip:8001960@sipgate.de>;tag=4004035317-2599214682
To: <sip:8001960@sipgate.de>;tag=b11cb9bb270104b49a99a995b8c68544.bb1c
Call-ID: 102790059@00:a0:57:11:a5:43
CSeq: 2 REGISTER
Contact: <sip:8001960@84.187.193.236:38518>;q=0.00;expires=240
Server: sipgate ser
Content-Length: 0
Warning: 392 217.10.79.9:5060 "Noisy feedback tells: pid=25003 req_src_ip=84.187.193.236 req_src_port=38518 in_uri=sip:sipgate.de out_uri=sip:sipgate.de via_cnt==1"

So das wars. Wäre schön, wenn sich die Fehler bald finden würden.

Gruss
Jochen
Nach oben
COMCARGRU
Beiträge: 1203
Registriert: 10 Nov 2004, 17:56
Wohnort: Hessen

Beitrag von COMCARGRU »

Metadiskussion LED Farben!

Auch dazu mein Statement: rötliche Farbtöne (also auch Orange), sollten definitiv für keine normalen Funktionszustände benutzt werden. Rot heißt immer, da ist was faul.

Auch oder gerade wenn solche Geräte in einem Serverraum stehen, sollte das tunlichst vermieden werden.

Wer seinen Serverraum kontrolliert schaut auf Farben. Ist alles Grün - wunderbar...

Ist da aber eine Gelbe, Rote oder Orangene LED dabei...

Gruß
COMCARGRU
Wann zum Teufel werden ALLE PCs grundsätzlich nur noch mit Hardware RAID 1 ausgestattet???
Nach oben
jhilgers
Beiträge: 175
Registriert: 02 Mär 2005, 14:39
Wohnort: Aachen

Beitrag von jhilgers »

Hi COMCARGU,

auch ich finde dieses organge-farbener Geflacker sehr irritierend :-(

Gruss
Jochen
Nach oben
jhilgers
Beiträge: 175
Registriert: 02 Mär 2005, 14:39
Wohnort: Aachen

Beitrag von jhilgers »

Hi nochmals,

gibt es noch keine Erkenntnisse wegen den offenen Problemen??? Würde schon gerne mal Anrufe annehmen können :-)

Gruss
Jochen
Nach oben
Benutzeravatar
Dilbert
Beiträge: 86
Registriert: 29 Mai 2005, 13:02

Beitrag von Dilbert »

eddia hat geschrieben:ich scheine offenbar nicht der einzige zu sein, der dadurch irritiert ist. Und ich bin mir sicher, dass 99,9% der zukünftigen 1722 Besitzer genauso denken werden. Und vielleicht bewirkt das ja ein Umdenken bei denen 'von Oben'. :-)
Hi,
ich möchte mich den 99,9% anschließen! Mich hat das auch verwirrt...

- Dilbert -
Bild

LC1823 mit DSL16000 (T-Online), L54g
Nach oben
Antworten

Zurück zu „Fragen zu LANCOM Systems VoIP Router“