[GELÖST]SIPGATE-ID in PURtel-Registrierung

[Rocky512]

Sent to udp:62.241.35.170:5060 at 4/12/2004 10:38:28:600 (730 bytes):

REGISTER sip:deu1.purtel.com SIP/2.0
Via: SIP/2.0/UDP 83.XXX.XXX.XXX:41045;branch=z9hG4bK-yuw6o8xsuf6z;rport
From: "PURTEL-ID" <sip:[email protected]>;tag=26642biy7z
To: "PURTEL-ID" <sip:[email protected]>
Call-ID: 3c26701a8647-l3ikg71zmxhg@83-169-139-30
CSeq: 9 REGISTER
Max-Forwards: 70
Contact: <sip:[email protected]:41045;transport=udp;line=adunvjlj>;q=1.0
User-Agent: snom190-3.56k
P-NAT-Refresh: 15
Supported: gruu
Allow-Events: dialog
X-Real-IP: XXX.XXX.XXX.XXX
WWW-Contact: <https://XXX.XXX.XXX.XXX:443>
Authorization: Digest username="PURTEL-ID",realm="deu1.purtel.com",nonce="5e709849",uri="sip:deu1.purtel.com",response="260d73ac454dc68f558d9142f151ef19",algorithm=md5
Expires: 600
Content-Length: 0




--------------------------------------------------------------------------------

Received from udp:62.241.35.170:5060 at 4/12/2004 10:38:28:670 (433 bytes):

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 83.XXX.XXX.XXX:41045;branch=z9hG4bK-yuw6o8xsuf6z;received=83.XXX.XXX.XXX;rport=5060
From: "PURTEL-ID" <sip:[email protected]>;tag=26642biy7z
To: "PURTEL-ID" <sip:[email protected]>;tag=as4f8d6506
Call-ID: 3c26701a8647-l3ikg71zmxhg@83-169-139-30
CSeq: 9 REGISTER
User-Agent: PURtel
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Contact: <sip:[email protected]>
Content-Length: 0




--------------------------------------------------------------------------------

Received from udp:62.241.35.170:5060 at 4/12/2004 10:38:28:680 (526 bytes):

SIP/2.0 200 OK
Via: SIP/2.0/UDP 83.XXX.XXX.XXX:41045;branch=z9hG4bK-yuw6o8xsuf6z;received=83.XXX.XXX.XXX;rport=5060
From: "PURTEL-ID" <sip:[email protected]>;tag=26642biy7z
To: "PURTEL-ID" <sip:PUR[email protected]>;tag=as4f8d6506
Call-ID: 3c26701a8647-l3ikg71zmxhg@83-169-139-30
CSeq: 9 REGISTER
User-Agent: PURtel
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Expires: 600
Contact: <sip:[email protected]:41045;transport=udp;line=adunvjlj>;expires=600
Date: Sat, 04 Dec 2004 09:38:29 GMT
Content-Length: 0




--------------------------------------------------------------------------------

Received from udp:62.241.35.170:5060 at 4/12/2004 10:38:28:920 (418 bytes):

OPTIONS sip:83.XXX.XXX.XXX SIP/2.0
Via: SIP/2.0/UDP 62.241.35.170:5060;branch=z9hG4bK4d8808c2
From: "purtel" <sip:[email protected]>;tag=as704c4b66
To: <sip:83.XXX.XXX.XXX>
Contact: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 102 OPTIONS
User-Agent: PURtel
Date: Sat, 04 Dec 2004 09:38:29 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Content-Length: 0




--------------------------------------------------------------------------------

Sent to udp:62.241.35.170:5060 at 4/12/2004 10:38:28:930 (560 bytes):

SIP/2.0 200 OK
Via: SIP/2.0/UDP 62.241.35.170:5060;branch=z9hG4bK4d8808c2
From: "purtel" <sip:[email protected]>;tag=as704c4b66
To: <sip:83.XXX.XXX.XXX>
Call-ID: [email protected]
CSeq: 102 OPTIONS
Contact: <sip:[highlight=red]SIPGATE-ID[/highlight]@83.XXX.XXX.XXX:41045;transport=udp;line=43wzo4pj>
User-Agent: snom190-3.56k
Accept-Language: en
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO
Allow-Events: talk, hold, refer
Supported: timer, 100rel, replaces
Content-Length: 0

Was hat eigentlich meine SIPGATE-ID in der Purtel-Registrierung zu suchen :roll:
@ mod
bitte mal verschieben ----> Snom

Edit von Christoph: Aus "quote" habe ich "code" gemacht.

 

[PURtel.com]

Frag das mal Dein Snom...

Das kommt ja von Dir!

 

[der_Gersthofer]

Versuch doch mal, nach einem Factory reset zunächst nur Leitung 1 mit PURtel zu füttern was dann passiert.
Läuft dann alles rund, dann gib in Leitung 2 nach Sipgate dazu was dann rauskommt...

 

[Rocky512]

werd ich heute Abend oder Morgen mal testen - bin im Moment schon eigentlich nicht mehr hier :wink:



___________________
edit 12:40

Da mann so schnell nicht aufgibt - Reset gemacht und nur Purtel konfiguriert, jetzt sieht das SIP-Protokoll für mich als nicht Profi i.O. aus.

Auch nach dem Konfigurieren des Sipgate-Accounts passiert in dieser Beziehung nichts ungewöhnliches mehr.

Aber leider noch die selben Probleme wie Hier beschrieben, warten wir mal die Antworten von SNOM und Purtel ab.