Jump to content

snom 300 problem to register on snome one free


zanf
 Share

Recommended Posts

I have a snom 300, this is the system information:

System Information:

Phone Type: snom300-SIP

MAC-Address: 000413254575

IP-Address: 192.168.0.11

Firmware-Version: snom300-SIP 7.3.30 6057

 

I try to register snom 330 to a snome one free bat the registration fails.

Someone tell me what is the problem? thanks.

 

This is the trace on snome one:

 

0] 2011/05/02 18:06:19: SIP Rx udp:192.168.0.11:5060:

REGISTER sip:192.168.0.10 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-dzec7f8436i0;rport

From: "203" <sip:203@192.168.0.10>;tag=rtxxotnwcj

To: "203" <sip:203@192.168.0.10>

Call-ID: 3c267148d49b-kri6imx7mwe5

CSeq: 4 REGISTER

Max-Forwards: 70

Contact: <sip:203@192.168.0.11:5060;line=0zsje7jv>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:48518a63-ee4e-4abc-8c61-06fc6292f523>";audio;mobility="fixed";duplex="full";description="snom300";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

User-Agent: snom300/7.3.30

Supported: gruu

Allow-Events: dialog

X-Real-IP: 192.168.0.11

Expires: 3600

Content-Length: 0

 

 

[0] 2011/05/02 18:06:19: SIP Tr udp:192.168.0.11:5060:

SIP/2.0 401 Authentication Required

Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-dzec7f8436i0;rport=5060

From: "203" <sip:203@192.168.0.10>;tag=rtxxotnwcj

To: "203" <sip:203@192.168.0.10>;tag=211ba45146

Call-ID: 3c267148d49b-kri6imx7mwe5

CSeq: 4 REGISTER

User-Agent: snom-PBX/4.2.0.3950

WWW-Authenticate: Digest realm="192.168.0.10",nonce="e7642be6308b44fde3580e56138981c5",domain="sip:192.168.0.10",algorithm=MD5

Content-Length: 0

Link to comment
Share on other sites

I have update teh Snome 300 with the last 8.4.18 ver. bat the problem is the same.

 

 

THIS IS THE TRACE ON SNOM 300:

 

Sent to udp:192.168.0.10:5060 at 3/5/2011 22:37:48:451 (703 bytes):

 

REGISTER sip:192.168.0.10 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-aakqt1xl6gtw;rport

From: "203" <sip:203@192.168.0.10>;tag=ek1vrobzqc

To: "203" <sip:203@192.168.0.10>

Call-ID: 3c26702226fe-juzcspp9dlpd

CSeq: 45 REGISTER

Max-Forwards: 70

Contact: <sip:203@192.168.0.11:5060;line=ee3ms4vf>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:9ca18f02-2dad-47e1-830a-2309411ed61b>";audio;mobility="fixed";duplex="full";description="snom300";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

User-Agent: snom300/8.4.18

Allow-Events: dialog

X-Real-IP: 192.168.0.11

Supported: path, gruu

Expires: 3600

Content-Length: 0

 

 

 

 

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

 

Sent to udp:192.168.0.10:5060 at 3/5/2011 22:37:52:462 (703 bytes):

 

REGISTER sip:192.168.0.10 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-aakqt1xl6gtw;rport

From: "203" <sip:203@192.168.0.10>;tag=ek1vrobzqc

To: "203" <sip:203@192.168.0.10>

Call-ID: 3c26702226fe-juzcspp9dlpd

CSeq: 45 REGISTER

Max-Forwards: 70

Contact: <sip:203@192.168.0.11:5060;line=ee3ms4vf>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:9ca18f02-2dad-47e1-830a-2309411ed61b>";audio;mobility="fixed";duplex="full";description="snom300";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

User-Agent: snom300/8.4.18

Allow-Events: dialog

X-Real-IP: 192.168.0.11

Supported: path, gruu

Expires: 3600

Content-Length: 0

 

 

 

 

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

 

Sent to udp:192.168.0.10:5060 at 3/5/2011 22:37:56:471 (703 bytes):

 

REGISTER sip:192.168.0.10 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-aakqt1xl6gtw;rport

From: "203" <sip:203@192.168.0.10>;tag=ek1vrobzqc

To: "203" <sip:203@192.168.0.10>

Call-ID: 3c26702226fe-juzcspp9dlpd

CSeq: 45 REGISTER

Max-Forwards: 70

Contact: <sip:203@192.168.0.11:5060;line=ee3ms4vf>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:9ca18f02-2dad-47e1-830a-2309411ed61b>";audio;mobility="fixed";duplex="full";description="snom300";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

User-Agent: snom300/8.4.18

Allow-Events: dialog

X-Real-IP: 192.168.0.11

Supported: path, gruu

Expires: 3600

Content-Length: 0

 

 

THIS IS THE TRACE ON SNOM ONE:

 

0] 2011/05/03 16:37:34: SIP Rx udp:192.168.0.11:5060:

REGISTER sip:192.168.0.10 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-aakqt1xl6gtw;rport

From: "203" <sip:203@192.168.0.10>;tag=ek1vrobzqc

To: "203" <sip:203@192.168.0.10>

Call-ID: 3c26702226fe-juzcspp9dlpd

CSeq: 45 REGISTER

Max-Forwards: 70

Contact: <sip:203@192.168.0.11:5060;line=ee3ms4vf>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:9ca18f02-2dad-47e1-830a-2309411ed61b>";audio;mobility="fixed";duplex="full";description="snom300";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

User-Agent: snom300/8.4.18

Allow-Events: dialog

X-Real-IP: 192.168.0.11

Supported: path, gruu

Expires: 3600

Content-Length: 0

 

 

[0] 2011/05/03 16:37:34: SIP Tx udp:192.168.0.11:5060:

SIP/2.0 401 Authentication Required

Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-aakqt1xl6gtw;rport=5060

From: "203" <sip:203@192.168.0.10>;tag=ek1vrobzqc

To: "203" <sip:203@192.168.0.10>;tag=51160fe97d

Call-ID: 3c26702226fe-juzcspp9dlpd

CSeq: 45 REGISTER

User-Agent: snom-PBX/4.2.0.3950

WWW-Authenticate: Digest realm="192.168.0.10",nonce="b7acb52a2e389bee872aab806ce19eb7",domain="sip:192.168.0.10",algorithm=MD5

Content-Length: 0

 

 

[0] 2011/05/03 16:37:35: SIP Rx udp:192.168.0.11:5060:

REGISTER sip:192.168.0.10 SIP/2.0

Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-aakqt1xl6gtw;rport

From: "203" <sip:203@192.168.0.10>;tag=ek1vrobzqc

To: "203" <sip:203@192.168.0.10>

Call-ID: 3c26702226fe-juzcspp9dlpd

CSeq: 45 REGISTER

Max-Forwards: 70

Contact: <sip:203@192.168.0.11:5060;line=ee3ms4vf>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:9ca18f02-2dad-47e1-830a-2309411ed61b>";audio;mobility="fixed";duplex="full";description="snom300";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

User-Agent: snom300/8.4.18

Allow-Events: dialog

X-Real-IP: 192.168.0.11

Supported: path, gruu

Expires: 3600

Content-Length: 0

 

 

[0] 2011/05/03 16:37:35: SIP Tr udp:192.168.0.11:5060:

SIP/2.0 401 Authentication Required

Via: SIP/2.0/UDP 192.168.0.11:5060;branch=z9hG4bK-aakqt1xl6gtw;rport=5060

From: "203" <sip:203@192.168.0.10>;tag=ek1vrobzqc

To: "203" <sip:203@192.168.0.10>;tag=51160fe97d

Call-ID: 3c26702226fe-juzcspp9dlpd

CSeq: 45 REGISTER

User-Agent: snom-PBX/4.2.0.3950

WWW-Authenticate: Digest realm="192.168.0.10",nonce="b7acb52a2e389bee872aab806ce19eb7",domain="sip:192.168.0.10",algorithm=MD5

Content-Length: 0

 

 

CAN YOU HELP ME ?

Link to comment
Share on other sites

I would suggest that you use plug and play. Essentially set the setting server (in advanced/update on the web interface of the phone, don't ask me why this is hidden there) to the IP address of the PBX. For example, put "192.168.0.10" there. If you try to manually configure everything, it might take a long time until all settings are set up the right way.

Link to comment
Share on other sites

I used the PnP bat the problem is the same.

 

I think it is a problem of protocol,

this is the log on SNOM 300:

 

5] 4/5/2011 23:30:30: sip::closed_reg_connection: reregister timer for line 0 set to 54 s

[5] 4/5/2011 23:30:30: SIP: transport error: 1000000 -> tls:192.168.0.10:5061

[5] 4/5/2011 23:30:30: SIP: final transport error: 1000000 -> tls:192.168.0.10:5061

[2] 4/5/2011 23:30:30: Transport Error: Pending packet 1000000: generating fake

[2] 4/5/2011 23:30:30: Registrar 204@192.168.0.10 timed out

[5] 4/5/2011 23:30:36: Settings applied!

[5] 4/5/2011 23:30:39: send lldp advertisment

[5] 4/5/2011 23:31:39: send lldp advertisment

[5] 4/5/2011 23:31:42: sip::closed_reg_connection: reregister timer for line 0 set to 52 s

[5] 4/5/2011 23:31:42: SIP: transport error: 1000002 -> tls:192.168.0.10:5061

[5] 4/5/2011 23:31:42: SIP: final transport error: 1000002 -> tls:192.168.0.10:5061

[2] 4/5/2011 23:31:42: Transport Error: Pending packet 1000002: generating fake

[2] 4/5/2011 23:31:42: Registrar 204@192.168.0.10 timed out

[5] 4/5/2011 23:32:39: send lldp advertisment

[5] 4/5/2011 23:32:51: sip::closed_reg_connection: reregister timer for line 0 set to 79 s

[5] 4/5/2011 23:32:51: SIP: transport error: 1000004 -> tls:192.168.0.10:5061

[5] 4/5/2011 23:32:51: SIP: final transport error: 1000004 -> tls:192.168.0.10:5061

[2] 4/5/2011 23:32:51: Transport Error: Pending packet 1000004: generating fake

[2] 4/5/2011 23:32:51: Registrar 204@192.168.0.10 timed out

[5] 4/5/2011 23:33:33: sip::closed_reg_connection: reregister timer for line 0 set to 67 s

[5] 4/5/2011 23:33:33: SIP: transport error: 1000006 -> tls:192.168.0.10:5061

[5] 4/5/2011 23:33:33: SIP: final transport error: 1000006 -> tls:192.168.0.10:5061

[2] 4/5/2011 23:33:33: Transport Error: Pending packet 1000006: generating fake

[2] 4/5/2011 23:33:33: Registrar 204@192.168.0.10 timed out

[5] 4/5/2011 23:33:36: Settings applied!

[5] 4/5/2011 23:33:39: send lldp advertisment

[5] 4/5/2011 23:34:39: send lldp advertisment

[5] 4/5/2011 23:34:48: sip::closed_reg_connection: reregister timer for line 0 set to 54 s

[5] 4/5/2011 23:34:48: SIP: transport error: 1000008 -> tls:192.168.0.10:5061

[5] 4/5/2011 23:34:48: SIP: final transport error: 1000008 -> tls:192.168.0.10:5061

[2] 4/5/2011 23:34:48: Transport Error: Pending packet 1000008: generating fake

[2] 4/5/2011 23:34:48: Registrar 204@192.168.0.10 timed out

 

thanks

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...