SIP-Protokoll "TP Parser error 32" - und kein REGISTER
Mitlerweile ist es mir gelungen, das Sip-Log zwischen dem F1000g und der Linksys SPA-9000 auszulesen. Nach diversen messages, kommen regelmäßig "TP Parser error: 32" Fehler darin vor - ganz unten bei der folgenden Auflistung. Ich glaube, das könnte der Grund dafür sein, warum das F1000g nur ständig "registering via..." anzeigt.
Leider kann ich diesen Fehlereintrag nicht genau deuten. Kennt Jemand von euch diesen Fehlereintrag???
Könnte es sein, daß trotz der genormten SIP-Protokolle, die beiden Geräte inkompatibel zu einander sind?
Hier mal ein Teil des Protokolls der SPA-9000 und zwischen F1000g:
syslog server(port:514) started on Sun Jun 18 18:51:42 2006
[pxy]<<192.168.0.50:6060(379)
[pxy]<<192.168.0.50:6060(379)
REGISTER sip:192.168.0.1 SIP/2.0Via: SIP/2.0/UDP 192.168.0.50:6060;rport;branch=z9hG4bK4078720503
From: <sip:
[email protected]>;tag=3101735862To: <sip:
[email protected]>
Call-ID:
[email protected]
CSeq: 1 REGISTER
Contact: <sip:
[email protected]:6060>;action=proxy
max-forwards: 70
expires: 60
user-agent: UTSTARCOM F1000/Device ID-0007ba25dacc
Content-Length: 0
[pxy]->192.168.0.50:6060
[pxy]->192.168.0.50:6060
SIP/2.0 200 OK
To: <sip:
[email protected]>;tag=41a7-0
From: <sip:
[email protected]>;tag=3101735862
Call-ID:
[email protected]
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.0.50:6060;branch=z9hG4bK4078720503;rport=6060
Contact: sip:
[email protected]:6060;expires=60
Server: Linksys/SPA9000-3.2.8(d)
Allow-Events: talk, hold, conference
Content-Length: 0
Date: Mon, 1 Jan 2003 4:0:51 PST
[pxy]<<192.168.0.50:6060(379)
[pxy]<<192.168.0.50:6060(379)
REGISTER sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.50:6060;rport;branch=z9hG4bK4078720503
From: <sip:
[email protected]>;tag=3101735862
To: <sip:
[email protected]>
Call-ID:
[email protected]
CSeq: 1 REGISTER
Contact: <sip:
[email protected]:6060>;action=proxy
max-forwards: 70
expires: 60
user-agent: UTSTARCOM F1000/Device ID-0007ba25dacc
Content-Length: 0
[pxy]->192.168.0.50:6060
[pxy]->192.168.0.50:6060
SIP/2.0 200 OK
To: <sip:
[email protected]>;tag=41a7-0
From: <sip:
[email protected]>;tag=3101735862
Call-ID:
[email protected]
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.0.50:6060;branch=z9hG4bK4078720503;rport=6060
Contact: sip:
[email protected]:6060;expires=60
Server: Linksys/SPA9000-3.2.8(d)
Allow-Events: talk, hold, conference
Content-Length: 0
Date: Mon, 1 Jan 2003 4:0:52 PST
[pxy]<<192.168.0.50:6060(379)
[pxy]<<192.168.0.50:6060(379)
REGISTER sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.50:6060;rport;branch=z9hG4bK4078720503
From: <sip:
[email protected]>;tag=3101735862
To: <sip:
[email protected]>
Call-ID:
[email protected]
CSeq: 1 REGISTER
Contact: <sip:
[email protected]:6060>;action=proxy
max-forwards: 70
expires: 60
user-agent: UTSTARCOM F1000/Device ID-0007ba25dacc
Content-Length: 0
[pxy]->192.168.0.50:6060
[pxy]->192.168.0.50:6060
SIP/2.0 200 OK
To: <sip:
[email protected]>;tag=41a7-0
From: <sip:
[email protected]>;tag=3101735862
Call-ID:
[email protected]
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.0.50:6060;branch=z9hG4bK4078720503;rport=6060
Contact: sip:
[email protected]:6060;expires=60
Server: Linksys/SPA9000-3.2.8(d)
Allow-Events: talk, hold, conference
Content-Length: 0
Date: Mon, 1 Jan 2003 4:0:53 PST
[pxy]<<192.168.0.50:6060(379)
[pxy]<<192.168.0.50:6060(379)
REGISTER sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.50:6060;rport;branch=z9hG4bK4078720503
From: <sip:
[email protected]>;tag=3101735862
To: <sip:
[email protected]>
Call-ID:
[email protected]
CSeq: 1 REGISTER
Contact: <sip:
[email protected]:6060>;action=proxy
max-forwards: 70
expires: 60
user-agent: UTSTARCOM F1000/Device ID-0007ba25dacc
Content-Length: 0
[pxy]->192.168.0.50:6060
[pxy]->192.168.0.50:6060
SIP/2.0 200 OK
To: <sip:
[email protected]>;tag=41a7-0
From: <sip:
[email protected]>;tag=3101735862
Call-ID:
[email protected]
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.0.50:6060;branch=z9hG4bK4078720503;rport=6060
Contact: sip:
[email protected]:6060;expires=60
Server: Linksys/SPA9000-3.2.8(d)
Allow-Events: talk, hold, conference
Content-Length: 0
Date: Mon, 1 Jan 2003 4:0:55 PST
[pxy]<<192.168.0.50:6060(379)
[pxy]<<192.168.0.50:6060(379)
REGISTER sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.50:6060;rport;branch=z9hG4bK4078720503
From: <sip:
[email protected]>;tag=3101735862
To: <sip:
[email protected]>
Call-ID:
[email protected]
CSeq: 1 REGISTER
Contact: <sip:
[email protected]:6060>;action=proxy
max-forwards: 70
expires: 60
user-agent: UTSTARCOM F1000/Device ID-0007ba25dacc
Content-Length: 0
[pxy]->192.168.0.50:6060
[pxy]->192.168.0.50:6060
SIP/2.0 200 OK
to: <sip:
[email protected]>;tag=41a7-0
From: <sip:
[email protected]>;tag=3101735862
Call-ID:
[email protected]
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.0.50:6060;branch=z9hG4bK4078720503;rport=6060
Contact: sip:
[email protected]:6060;expires=60
Server: Linksys/SPA9000-3.2.8(d)
Allow-Events: talk, hold, conference
Content-Length: 0
Date: Mon, 1 Jan 2003 4:0:59 PST
[pxy]<<192.168.0.50:6060(2)
[pxy]<<192.168.0.50:6060(2)
TP Parser error: 32
TP Parser error: 32
[pxy]<<192.168.0.50:6060(379)
[pxy]<<192.168.0.50:6060(379)
REGISTER sip:192.168.0.1 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.50:6060;rport;branch=z9hG4bK4078720503
From: <sip:
[email protected]>;tag=3101735862
To: <sip:
[email protected]>
Call-ID:
[email protected]
CSeq: 1 REGISTER
Contact: <sip:
[email protected]:6060>;action=proxy
max-forwards: 70
expires: 60
user-agent: UTSTARCOM F1000/Device ID-0007ba25dacc
Content-Length: 0
....und so weiter.....
Gruß Burkhard