Lisence no connecting

[qvs5010]

Hi

 

I have a Snom Plus,

 

I put my license key in my the license text box.

 

Then I go and check by Status, and it shows no license.

 

 

And my logs show:

 

[8] 2012/06/15 14:25:46: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:25:46: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:25:46: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:25:46: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:25:46: Cannot send packet: No license

[0] 2012/06/15 14:26:18: Last message repeated 11 times

[5] 2012/06/15 14:26:18: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:27:14: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:27:14: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:27:14: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:27:14: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:27:14: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:27:14: Cannot send packet: No license

[0] 2012/06/15 14:27:46: Last message repeated 11 times

[5] 2012/06/15 14:27:46: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:28:43: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:28:43: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:28:43: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:28:43: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:28:43: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:28:43: Cannot send packet: No license

[0] 2012/06/15 14:29:15: Last message repeated 11 times

[5] 2012/06/15 14:29:15: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:30:12: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:30:12: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:30:12: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:30:12: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:30:12: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:30:12: Cannot send packet: No license

[0] 2012/06/15 14:30:44: Last message repeated 11 times

[5] 2012/06/15 14:30:44: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:31:40: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:31:40: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:31:40: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:31:40: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:31:40: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:31:40: Cannot send packet: No license

[0] 2012/06/15 14:32:12: Last message repeated 11 times

[5] 2012/06/15 14:32:12: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:33:09: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:33:09: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:33:09: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:33:09: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:33:09: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:33:09: Cannot send packet: No license

[0] 2012/06/15 14:33:41: Last message repeated 11 times

[5] 2012/06/15 14:33:41: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:34:38: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:34:38: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:34:38: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:34:38: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:34:38: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:34:38: Cannot send packet: No license

[0] 2012/06/15 14:35:10: Last message repeated 11 times

[5] 2012/06/15 14:35:10: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:36:07: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:36:07: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:36:07: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:36:07: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:36:07: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:36:07: Cannot send packet: No license

[0] 2012/06/15 14:36:38: Last message repeated 11 times

[5] 2012/06/15 14:36:38: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:37:35: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:37:35: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:37:35: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:37:35: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:37:35: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:37:35: Cannot send packet: No license

[0] 2012/06/15 14:38:07: Last message repeated 11 times

[5] 2012/06/15 14:38:07: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:38:08: DNS: Request rabbit-ssl2.snom.com from server 41.193.4.170

[8] 2012/06/15 14:38:08: DNS: Add AAAA rabbit-ssl2.snom.com (ttl=60)

[8] 2012/06/15 14:38:09: HTTP client: Connect to 188.40.44.96:443, pending requests 0

[8] 2012/06/15 14:39:04: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:39:04: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:39:04: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:39:04: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:39:04: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:39:04: Cannot send packet: No license

[0] 2012/06/15 14:39:08: Last message repeated 4 times

[8] 2012/06/15 14:39:08: DNS: AAAA rabbit-ssl2.snom.com expired

[0] 2012/06/15 14:39:11: Cannot send packet: No license

[0] 2012/06/15 14:39:36: Last message repeated 7 times

[5] 2012/06/15 14:39:36: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

[8] 2012/06/15 14:40:33: Trunk 4: Preparing for re-registration

[8] 2012/06/15 14:40:33: Trunk 4: sending discover message for 41.193.4.170

[8] 2012/06/15 14:40:33: Trunk 4: Received reply for discover method

[8] 2012/06/15 14:40:33: Trunk 4 (Logicalout1) is associated with the following addresses: udp:41.193.4.170:5060

[8] 2012/06/15 14:40:33: Trunk Logicalout1: Sending registration to 41.193.4.170

[0] 2012/06/15 14:40:33: Cannot send packet: No license

[0] 2012/06/15 14:41:05: Last message repeated 11 times

[5] 2012/06/15 14:41:05: Registration on trunk 4 (Logicalout1) failed. Retry in 60 seconds

 

 

 

[0] 2012/06/15 18:42:27: Cannot send packet: No license

[0] 2012/06/15 18:43:13: Last message repeated 11 times

[0] 2012/06/15 18:43:13: Administrator logged in from IP address 192.168.168.252, session n3b2brsd57koegcuuqg7

[0] 2012/06/15 18:43:59: Cannot send packet: No license

[0] 2012/06/15 18:50:53: Last message repeated 55 times

[0] 2012/06/15 18:50:53: Administrator logged in from IP address 192.168.168.242, session 691ohsokh8jzm0ciyx1k

[0] 2012/06/15 18:51:39: Cannot send packet: No license

[qvs5010]

I have put my license key in with Capital letters.

 

XXX-XXX-XXX-XXX

[Vodia PBX]

It should not make a difference. However, if you have a snom free license (and not the latest software version), you should enter an empty "manual" key, so that it would go to the right license server. After that, you should be able to acticate the code.

 

Because the PBX keeps the entered code in a setting, changing the upper/lower case makes the PBX detect a change and re-load the key from the server. Again, this behavior was also changed/fixed in the latest version; so in the future this process should be easier.

[qvs5010]

I did all that and no luck, it just doesn't want to connect to the Activation Server.

[Vodia PBX]

Contact the local support, and they will get you a manual activation key then. Also, if you can, upgrade to 4.5 Delta which has an improved HTTP client.