SNOM D715 Not Connecting

Discussion in '3CX Phone System - General' started by malone, May 30, 2016.

Thread Status:
Not open for further replies.
  1. malone

    Joined:
    May 30, 2016
    Messages:
    6
    Likes Received:
    0
    All of our SNOM D715 phones are having the below issue connecting to a internal 3CX server - any ideas? The auto provisioning appears to be working...

    Note also the phones are not appearing in the auto provisioning page of 3CX - they have to be manually added.



    May 29 23:34:36 [INFO ] PHN: ProvisioningReplacements: URL >http://pbx.example.com.au:5000/provisioning/biugn9fn0s/firmware/snom/snom715.xml<
    May 29 23:34:36 [DEBUG0] PHN: Uri Replace >{mac}< in >http://pbx.example.com.au:5000/provisioning/biugn9fn0s/firmware/snom/snom715.xml<
    May 29 23:34:36 [DEBUG0] PHN: Uri Replaced result: >http://pbx.example.com.au:5000/provisioning/biugn9fn0s/firmware/snom/snom715.xml<
    May 29 23:34:36 [DEBUG0] PHN: ReplaceQueryVariables in >http://pbx.example.com.au:5000/provisioning/biugn9fn0s/firmware/snom/snom715.xml<
    May 29 23:34:36 [DEBUG0] PHN: ReplaceQueryVariables replaced: >http://pbx.example.com.au:5000/provisioning/biugn9fn0s/firmware/snom/snom715.xml<
    May 29 23:34:36 [NOTICE] PHN: Fetching FW URL: http://pbx.example.com.au:5000/provisio ... nom715.xml
    May 29 23:34:36 [NOTICE] PHN: Fetching URL: http://pbx.example.com.au:5000/provisio ... nom715.xml
    May 29 23:34:36 [DEBUG2] WEBCLIENT: Send TCP none
    May 29 23:34:36 [DEBUG2] WEBCLIENT: Socket 23 connecting
    May 29 23:34:36 [NOTICE] PHN: Last provisioning was successful, thus stop here!
    May 29 23:34:36 [NOTICE] PHN: Go to wizzard if all settings have been read.
    May 29 23:34:36 [NOTICE] PHN: SetProvisioningDone
    May 29 23:34:36 [NOTICE] DNS: Starting dns proxy...
    May 30 09:34:36 [NOTICE] PHN: DST start 02.10.2016 02:00:00 end 03.04.2017 03:00:00 offset 3600
    May 30 09:34:36 [NOTICE] PHN: Setting automatic settings refresh timer with 86400 seconds
    May 30 09:34:38 [ERROR ] PHN: TPL: Socket Error: 22/33/connected, Tls error, closing
    May 30 09:34:38 [NOTICE] PHN: Fetching FW URL: http://pbx.example.com.au:5000/provisio ... rmware.htm
    May 30 09:34:38 [NOTICE] PHN: Fetching URL: http://pbx.example.com.au:5000/provisio ... rmware.htm
    May 30 09:34:38 [WARN ] SIP: transaction_timeout udp: 1000001 (32500)
    May 30 09:34:38 [ERROR ] SIP: transport error: 1000001 -> udp:10.0.0.11:5060
    May 30 09:34:38 [NOTICE] SIP: Add dirty host: udp:10.0.0.11:5060 (0 sec)
    May 30 09:34:38 [ERROR ] SIP: request 1000001 destination invalid udp:10.0.0.11:5060 3134363435363438373833313239-4nxigrb000d8
    May 30 09:34:38 [NOTICE] SIP: final transport error: 1000001 -> udp:10.0.0.11:5060
    May 30 09:34:38 [ERROR ] SIP: transport error 1000001: generating fake 599
    May 30 09:34:38 [ERROR ] SIP: Registrar 223@10.0.0.11:5060 timed out
    May 30 09:35:22 [NOTICE] PHN: DST start 02.10.2016 02:00:00 end 03.04.2017 03:00:00 offset 3600
    May 30 09:35:22 [NOTICE] CFG: Std-Settings stored
    May 30 09:35:22 [NOTICE] CFG: FKey-Settings stored
    May 30 09:35:22 [NOTICE] CFG: TBook stored
    May 30 09:38:45 [NOTICE] PHN: TPL: Socket 28 idle/connect timeout
    May 30 09:38:47 [NOTICE] PHN: TPL: Socket 26 idle/connect timeout
    May 30 09:38:47 [NOTICE] PHN: TPL: Socket 27 idle/connect timeout
    May 30 09:38:47 [NOTICE] PHN: TPL: Socket 29 idle/connect timeout
    May 30 09:38:47 [NOTICE] PHN: TPL: Socket 30 idle/connect timeout
    May 30 09:38:50 [NOTICE] PHN: TPL: Socket 31 idle/connect timeout
    May 30 09:38:54 [NOTICE] PHN: TPL: Socket 32 idle/connect timeout
    May 30 09:39:03 [NOTICE] PHN: TPL: Socket 33 idle/connect timeout
     
  2. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    5,425
    Likes Received:
    352
    Please make sure you are using the latest supported firmware on your Snom phones and read the following guide to make sure you are not missing something.

    http://www.3cx.com/sip-phones/snom-710-720-760/


    Now from what i see from the log you attached and a search through the web i can see that there may be a network topology issue since you can't see the phones in the phones tab, take a look into that.

    Also you may want to look into turning TCP fragmentation on in your network. Take a look in the Snom forums they have a few posts about this.
     
  3. malone

    Joined:
    May 30, 2016
    Messages:
    6
    Likes Received:
    0
    Already have the latest firmware. Will have a look at fragmentation. Network topology should not be an issue as it is a standard network - on the same subnet
     
  4. malone

    Joined:
    May 30, 2016
    Messages:
    6
    Likes Received:
    0
    Problem fixed by rebooting phones and server
     
Thread Status:
Not open for further replies.