Hello. I was able to register a D785 Snom phone with a Fortivoice 84B pbx, but while I am able to call other internal extensions connected to this pbx and perform outside calls, when I try to call the D785 phone from other extensions or from outside lines of this pbx, I get a busy signal even when in idle mode. Any suggestion? Thank you.
12 Comments
Federico Rossi
Dec 14, 2022Hi, we need the SIP trace and phone syslog to check what is happening. Please take the logs from the phone after an incoming call and attach them here, or better, open a ticket on the helpdesk platform: helpdesk.snom.com
Giuseppe Aloi
Dec 15, 2022Thank you Federico for your reply.
Here there are the logs:
SIP Trace:
Sent to Udp:192.168.1.12:5060 from Udp:192.168.1.98:48316 at Dec 15 08:51:27.058 (519 bytes):
SIP/2.0 481 Call/Transaction Does Not Exist
Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG4bKe1f788d5
From: "SIT TRAVEL GROUP" <sip:103@192.168.1.12>;tag=27638986313655792106
To: "SIT TRAVEL GROUP" <sip:108@192.168.1.12>;tag=36et91p65d
Call-ID: 147795092
CSeq: 1 ACK
User-Agent: snomD785/10.1.127.10
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE
Allow-Events: talk, hold, refer, call-info
Supported: timer, 100rel, replaces, from-change
Content-Length: 0
Log:
Dec 15 08:51:14.987 [NOTICE] PHN: TPL: Socket 31 idle/connect timeout
Dec 15 08:51:21.104 [NOTICE] PHN: TPL: Socket 32 idle/connect timeout
Dec 15 08:51:37.917 [NOTICE] PHN: TPL: Socket 33 idle/connect timeout
Dec 15 08:52:17.627 [NOTICE] PHN: TPL: Socket 34 idle/connect timeout
Dec 15 08:52:26.765 [CRITIC] PHN: Warning: Ignore invalid parameter: hidden_tag
Dec 15 08:52:26.766 [DEBUG0] CFG: apply_value: log_level = '9', need_apply: 0, provisioning (progress:0/finished:1), need reboot: 0
Dec 15 08:52:26.769 [INFOÂ ] PHN: new Tag: >4yostdszorhmmfa3< Filename: log.htm
Dec 15 08:52:28.942 [INFOÂ ] PHN: WEB: Request 35/815/0: POST /log.htm HTTP/1.1
Dec 15 08:52:28.943 [INFOÂ ] PHN: WEB: 35 Digest authentication
Dec 15 08:52:28.949 [DEBUG0] CFG: apply_value: callrecord_dialed_remote = '<sip:109@192.168.1.12;user=phone>', need_apply: 0, provisioning (progress:0/finished:1), need reboot: 0
Dec 15 08:52:28.949 [DEBUG0] CFG: apply_value: callrecord_dialed_period = '2022-12-13T06:18:09ZPT0S', need_apply: 0, provisioning (progress:0/finished:1), need reboot: 0
Dec 15 08:52:28.950 [DEBUG0] PHN: ContactUtils::GetVcard: identity=1
Dec 15 08:52:28.951 [DEBUG0] CFG: apply_value: callrecord_dialed_remote = '<sip:103@192.168.1.12;user=phone>', need_apply: 0, provisioning (progress:0/finished:1), need reboot: 0
Dec 15 08:52:28.951 [DEBUG0] CFG: apply_value: callrecord_dialed_period = '2022-12-10T10:04:00ZPT0S', need_apply: 0, provisioning (progress:0/finished:1), need reboot: 0
Dec 15 08:52:28.951 [DEBUG0] PHN: ContactUtils::GetVcard: identity=1
Dec 15 08:52:28.953 [DEBUG0] CFG: apply_value: callrecord_dialed_remote = '<sip:c11@192.168.1.12;user=phone>', need_apply: 0, provisioning (progress:0/finished:1), need reboot: 0
Dec 15 08:52:28.953 [DEBUG0] CFG: apply_value: callrecord_dialed_period = '2022-11-27T10:43:00ZPT3S', need_apply: 0, provisioning (progress:0/finished:1), need reboot: 0
Dec 15 08:52:28.954 [DEBUG0] PHN: ContactUtils::GetVcard: identity=1
Dec 15 08:52:28.955 [DEBUG0] PHN: ContactUtils::GetVcard: identity=1
Dec 15 08:52:28.956 [DEBUG0] PHN: ContactUtils::GetVcard: identity=1
Dec 15 08:52:28.964 [INFOÂ ] TOOLS: Going to write file ./snomconfig/config.xml.
Dec 15 08:52:28.974 [NOTICE] PHN: Std-Settings stored
Dec 15 08:52:28.977 [INFOÂ ] PHN: new Tag: >6dj9mszea2fwi3f6< Filename: log.htm
Thank you again for your help in this matter.
Best regards, Giuseppe Aloi.
Giuseppe Aloi
Jan 02, 2023Hello Federico, Happy New Year.
I submitted the log here some time ago, I tried to submit to helpdesk.snom.com but it seems it is reserved to Snom Partnes. Can you please help? I really appreciate it.
Federico Rossi
Jan 03, 2023Hi, could you post the complete sip trace? Is better to copy/paste the sip trace in a TXT file and attach it into the reply or upload the file in a cloud storage (dropbox, google drive) and post the link.
Giuseppe Aloi
Jan 03, 2023Hello Federico, thank you for your reply.
Here there is the file:
FortivoiceD785.txt
Please let me know if it works.
Thank you.
Federico Rossi
Jan 05, 2023Hi, is the extension configured on the phone 108?
Seems there is something wrong in the INVITE, you must also check the phone logs to have a clue
Giuseppe Aloi
Jan 07, 2023Hello Federico.
Yes, the extension is 108.
Here there is the phone log:
D785Log.txt
Thank you for your help in this matter.
Federico Rossi
Jan 10, 2023Ciao, ho controllato nel dettaglio e ho visto che nell'INVITE che fa il Forti non c'è la riga Allow
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
e nell'SDP nel Media Description (m) non è specificato che si tratta di una chiamata audio, ad esempio:
m= audio 64100 RTP/AVP 9 0 8 3 99 112 18 101
A meno di configurazioni anomale sul telefono sono le uniche cose che ho notato. Per sicurezza mi puoi mandare uno screenshot della pagina dell'identità o il file di configurazione xml del telefono?
Giuseppe Aloi
Jan 12, 2023Buongiorno Federico, grazie per la tua risposta.
Ecco qui il file .xml della configurazione del D785:
settings.xml
Grazie ancora per il tuo supporto.
Giuseppe Aloi
Jan 24, 2023Buongiorno Federico.
Ho inviato in precedenza file .xml del D785, come da te richiesto.
Hai avuto modo di visionarlo?
Grazie.
Federico Rossi
Jan 25, 2023Ciao, puoi banalmente provare a mettere 108 anche sullo user_realname, invece di SIT TRAVEL GROUP ?
Giuseppe Aloi
Jan 27, 2023Buongiorno Federico.
Dove trovo il campo user_realname? Al momento vedo SIT TRAVEL GROUP nel campo Display Name dell'interfaccia web. E' per caso la stessa di user_realname?
Grazie.