Jump to content
Vodia PBX forum
Cld007

Snom D765 Provisioning Not Working

Recommended Posts

Cld007    0

Hello,

 

We are using Vodia 5.3.2 on a hosted platform.

 

Having trouble provisioning a Snom D765.

 

This is part of the log file from the phone- (replaced actual domain with pbxuserdomain.com for privacy)

 

Jan 1 00:02:05 [NOTICE] PHN: Fetching URL: http://pbxuserdomain.com:80/snomD765.htm

Jan 1 00:02:05 [DEBUG2] WEBCLIENT: Send TCP none

Jan 1 00:02:05 [DEBUG2] WEBCLIENT: Socket 57 dns_resolving

Jan 1 00:02:05 [DEBUG2] PHN: TMR: setting up 'gui_state.cpp (811): [static void gui_object::DisplayStateCbAtNextLoop(void*, void*)]' 0x408d42fc to fire periodically every 500 ms

Jan 1 00:02:05 [DEBUG0] DNS: AddrInfo for 'pbxuserdomain.com' invalid, error: Name or service not known (-2)

Jan 1 00:02:05 [WARN ] PHN: Could not resolve host >pbxuserdomain.com<

Jan 1 00:02:05 [DEBUG2] WEBCLIENT: Socket 57 dns_resolve_cache_lookup_has_failed

Jan 1 00:02:05 [WARN ] WEBCLIENT: Could not resolve host pbxuserdomain.com

Jan 1 00:02:05 [DEBUG2] WEBCLIENT: Socket 57 disconnected

Jan 1 00:02:05 [DEBUG2] WEBCLIENT: Socket 57 deleted

Jan 1 00:02:05 [iNFO ] PHN: Config setup: code: 400, uri: http://pbxuserdomain.com:80/snomD765.htm

Jan 1 00:02:05 [NOTICE] PHN: SetProvisioningDone

Jan 1 00:02:05 [NOTICE] PHN: Config setup: return code 400; giving up on >http://pbxuserdomain.com:80/snomD765.htm<

Jan 1 00:02:05 [NOTICE] PHN: SetProvisioningDone

Do you have any ideas as to why the phone won't provision?

 

Many thanks for your help.

Share this post


Link to post
Share on other sites
Cld007    0

I replaced the correct domain with that is being used with - pbxuserdomain.com

 

The proper domain can be resolved fine.

 

Is it anything to do with not having d765 config file in the 5.3.2 version?

 

Or is it looking for the config file in the wrong place? It is looking for http://pbxuserdomain.com/snomD765.htm

Share this post


Link to post
Share on other sites
Vodia PBX    0

We did some major overhaul of the snom provisioning I believe it was after 5.3.2, because the new models were hard to cover plus the introduction of the letter "D" (or "d") was another headache. Any reason why you don't want to move to 5.4.0?

Share this post


Link to post
Share on other sites
Bersa    0

I Think i have the same problem with a Snom D745.

 

We are on Version: 5.3.2 (CentOS64)

 

Can we change it by our self? We are using hostedi.am or did you have to do it?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×