S705 Upgrade Issues

Hello,

I’m running into some firmware issues with a S705. The device is currently configured for Zero touch provisioning via HTTP, and I have the Firmware Slot 1 set to 1.54 (2.0.4.63) and Slot 2 1.53 (2.0.4.62). This device is brand new and was received with firmware version 3.0.4.55 installed, and I noticed it didn’t upgrade after it booted and provisioned, so I tried to manually upgrade it via the web interface on the phone itself.

as it was booting back up immediately after the manual upgrade I am able to login to the phone web interface see the new firmware version. but then it runs through checking firmware and downgrades back to 3.0.4.55. I cant explain what would b causing this, can anyone shed some light?

Im running Endpoint Manager 14.0.2.188 on FreePBX 14.0.11

After populating the firmware slots, did you select a firmware version in the template the phone provisions from? Sounds like it’s still set to ‘recommended’.

@lgaetz That is what it is set to, doesn’t that just tell it to decide best choice of the 2?

No. Recommended is a separate third slot which is managed independently by EPM. If you want the firmware from slot 1 or 1, you must explicitly set that in the template.

@lgaetz That’s good to know, I was not aware of that. Changing it to explicitly use Firmware Slot 1 worked.

Now the reason why I was chasing a firmware upgrade was i’m experiencing some weird disconnect issue. I have a S500 & S505 on the same network that don’t have issues, but this phone drops and plays a busy tone about 40 seconds into a call, I can replicate it dialing into voicemail even. I opened a continuous ping to the PBX from the computer plugged into the back of the phone and don’t see any packet loss either.

I checked the asterisk logs and just see the hangup, no crash errors or anything

[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx.c: Spawn extension (from-internal, *97, 120) exited non-zero on ‘PJSIP/110-0000002e’
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx.c: Executing [[email protected]:1] Macro(“PJSIP/110-0000002e”, “hangupcall”) in new stack
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx.c: Executing [[email protected]:1] GotoIf(“PJSIP/110-0000002e”, “1?theend”) in new stack
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx_builtins.c: Goto (macro-hangupcall,s,3)
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx.c: Executing [[email protected]:3] ExecIf(“PJSIP/110-0000002e”, “0?Set(CDR(recordingfile)=)”) in new stack
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx.c: Executing [[email protected]:4] NoOp(“PJSIP/110-0000002e”, " montior file= ") in new stack
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx.c: Executing [[email protected]:5] GotoIf(“PJSIP/110-0000002e”, “1?skipagi”) in new stack
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx_builtins.c: Goto (macro-hangupcall,s,7)
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx.c: Executing [[email protected]:7] Hangup(“PJSIP/110-0000002e”, “”) in new stack
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] app_macro.c: Spawn extension (macro-hangupcall, s, 7) exited non-zero on ‘PJSIP/110-0000002e’ in macro ‘hangupcall’
[2019-04-30 17:34:34] VERBOSE[27686][C-00000019] pbx.c: Spawn extension (from-internal, h, 1) exited non-zero on ‘PJSIP/110-0000002e’

Is this phone on the same firmware version as the other phones?

That won’t actually tell you what happened, start a capture on the phone, make the call, wait for it disconnect mid-call, stop and export it. See if you find there some clues.

This is not the full log, please post the full call log.

Highly unlikely to be a firmware issue. If there is nothing in the call trace, take a look at the signalling: Virtuous Signalling

@PitzKey First, yes the S505 and S500 are on the same firmware. Where can I pull the full call log? The CEL seems to show that the phone in question (ext 110) did hangup on this test call to 2003:

|Wed, May 1, 2019 8:41 PM|BRIDGE_EXIT|1556768421.1496|1556768421.1496|110|s|macro-dialout-trunk|PJSIP/110-0000003f|
|---|---|---|---|---|---|---|---|
|Wed, May 1, 2019 8:41 PM|BRIDGE_EXIT|1556768421.1497|1556768421.1496|2003|s|macro-dialout-trunk|IAX2/FreePBX-A-21644|
|Wed, May 1, 2019 8:41 PM|HANGUP|1556768421.1497|1556768421.1496|2003|s|macro-dialout-trunk|IAX2/FreePBX-A-21644|
|Wed, May 1, 2019 8:41 PM|CHAN_END|1556768421.1497|1556768421.1496|2003|s|macro-dialout-trunk|IAX2/FreePBX-A-21644|
|Wed, May 1, 2019 8:41 PM|HANGUP|1556768421.1496|1556768421.1496|110|h|from-internal|PJSIP/110-0000003f|
|Wed, May 1, 2019 8:41 PM|CHAN_END|1556768421.1496|1556768421.1496|110|h|from-internal|PJSIP/110-0000003f|
|Wed, May 1, 2019 8:41 PM|LINKEDID_END|1556768421.1496|1556768421.1496|110|h|from-internal|PJSIP/110-0000003f|
|Wed, May 1, 2019 8:40 PM|ANSWER|1556768421.1497|1556768421.1496|2003|2003|from-internal|IAX2/FreePBX-A-21644|
|Wed, May 1, 2019 8:40 PM|ANSWER|1556768421.1496|1556768421.1496|110|s|macro-dialout-trunk|PJSIP/110-0000003f|
|Wed, May 1, 2019 8:40 PM|BRIDGE_ENTER|1556768421.1497|1556768421.1496|2003|s|macro-dialout-trunk|IAX2/FreePBX-A-21644|
|Wed, May 1, 2019 8:40 PM|BRIDGE_ENTER|1556768421.1496|1556768421.1496|110|s|macro-dialout-trunk|PJSIP/110-0000003f|
|Wed, May 1, 2019 8:40 PM|CHAN_START|1556768421.1496|1556768421.1496|110|2003|from-internal|PJSIP/110-0000003f|
|Wed, May 1, 2019 8:40 PM|CHAN_START|1556768421.1497|1556768421.1496||s|default|IAX2/FreePBX-A-21644|

https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs-PartII

Additionally, take a look at the post Lorne linked here.

@PitzKey Did you mean to pin a link under the “here”?

Also, going through the CDR page and pulling the trace is the exact same data, I grabbed one of the other calls that hung up during that same set of attempts:

Time Event CNAM CNUM ANI DID AMA exten context App channel UserDefType EventExtra CEL Table
Wed, 1 May 2019 20:40 CHAN_START Office 110 DEFAULT 2003 from-internal PJSIP/110-0000003f
Wed, 1 May 2019 20:40 CHAN_START DEFAULT s default IAX2/FreePBX-A-21644
Wed, 1 May 2019 20:40 ANSWER CID:110 2003 DEFAULT 2003 from-internal AppDial IAX2/FreePBX-A-21644
Wed, 1 May 2019 20:40 ANSWER Office 110 110 2003 DEFAULT s macro-dialout-trunk Dial PJSIP/110-0000003f
Wed, 1 May 2019 20:40 BRIDGE_ENTER CID:110 2003 DEFAULT s macro-dialout-trunk AppDial IAX2/FreePBX-A-21644
Wed, 1 May 2019 20:40 BRIDGE_ENTER Office 110 110 2003 DEFAULT s macro-dialout-trunk Dial PJSIP/110-0000003f
Wed, 1 May 2019 20:41 BRIDGE_EXIT Office 110 110 2003 DEFAULT s macro-dialout-trunk Dial PJSIP/110-0000003f
Wed, 1 May 2019 20:41 BRIDGE_EXIT CID:110 2003 DEFAULT s macro-dialout-trunk AppDial IAX2/FreePBX-A-21644
Wed, 1 May 2019 20:41 HANGUP CID:110 2003 DEFAULT s macro-dialout-trunk AppDial IAX2/FreePBX-A-21644
Wed, 1 May 2019 20:41 CHAN_END CID:110 2003 DEFAULT s macro-dialout-trunk AppDial IAX2/FreePBX-A-21644
Wed, 1 May 2019 20:41 HANGUP Office 110 110 2003 DEFAULT h from-internal PJSIP/110-0000003f
Wed, 1 May 2019 20:41 CHAN_END Office 110 110 2003 DEFAULT h from-internal PJSIP/110-0000003f
Wed, 1 May 2019 20:41 LINKEDID_END Office 110 110 2003 DEFAULT h from-internal PJSIP/110-0000003f

I dumped the logs from the phone itself and was able to find the issue, there was an error on one of my NAT network statements (not sure why it wasn’t effecting the other devices). But in doing so I stumbled across a new string of interesting messages, it looks like it’s complaining about RTP and from what it’s saying it is trying to use my external IP address even though everything I can find is set to use internal. Any thoughts?

[05-02 19:44:24 52:50:05] MS: CodecType 0 Get Rtp Interval Fail!!!
[05-02 19:44:25 52:50:05] MS: CodecType 0 Get Rtp Interval Fail!!!
[05-02 19:44:26 52:50:05] MS: CodecType 0 Get Rtp Interval Fail!!!
[05-02 19:44:28 52:50:05] MS: CodecType 0 Get Rtp Interval Fail!!!
[05-02 19:44:28 52:50:05] SIP: aid 0 cb_send_message, host is NULL, will set it…
[05-02 19:44:28 52:50:05] SIP: aid 0 cb_send_message, no route, req_uri host:port is ExternalIP:5060

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.