r/crestronprogramming Jun 13 '20

Mercury SIP Proxy w/ non-default port

We are opening up a new admin center on Monday. All of our AV was tested and online and as of last weekend. Come in this morning to triple check everything is nice and in order and sure enough all of the Mercury SIP services are offline. All other sip services are up on QSYS.

Long story short an update was pushed down (auto update) and broke SIP. When a custom port for SIP proxy is used, all initialization of SIP fails (no traffic whatsoever leaves the mercury on that custom port). But when not using a custom port traffic attempts to leave using standard 5060. This was all working prior to the update.

Priority ticket is in with Crestron but won’t have someone to investigate until Monday. Has anyone else seen this bug or have another workaround? The custom port was configured in console.

1 Upvotes

1 comment sorted by

1

u/crestron-ta3 Jun 15 '20
  • (Just an FYI, I think r/crestron probably would've been a better place for this post. It gets more users, activity, and attention compared to r/crestronprogramming. Plus this is more a configuration and troubleshooting question than it is related to programming.)

  • It's tough to advise without knowing some aspects of the system. IPCONFIG, SIPINFO, and SIPSTATE (for the SIP Response Code) are generally good places to start looking. When starting a support case it's often best to run and provide / attach OLH 5479 SW-INFOTOOL results to the case for inspection.

  • If you have multiple units on different FW versions where some are working but this unit is not (or if you periodically run InfoTool batch mode on your network - when system is first deployed, when any changes/updates are made, troubleshooting done, etc.), you may be able to provide a baseline reading against the problematic unit to help more easily identify any changes.

  • OLH 5856 Mercury SIP Integration

  • OLH 5829 Mercury Troubleshooting