Use range pattern for custom SIP ports 6060-6061 to match standard ports

[Copilot]

Addresses feedback on firewall configuration asymmetry: port 5061 opens both TCP/UDP while port 6061 was opening TCP only.

Changes

• Added 6061/udp to the firewall configuration to match the configuration of port 5061
• Refactored to use range notation (6060-6061/tcp and 6060-6061/udp) to match the pattern used for standard ports (5060-5061)
• Both custom ports (6060 and 6061) now have consistent TCP/UDP support matching the standard ports (5060 and 5061)

# Open SIP (5060), SIPS (5061), custom port (6060,6061) and RTP range (10000-20000)
agent.assert_exp(agent.add_public_service(os.environ['MODULE_ID'], [
    "5060-5061/tcp",
    "5060-5061/udp",
    "6060-6061/tcp",
    "6060-6061/udp",
    "10000-20000/udp"]))

This change ensures consistency across all SIP ports in the firewall configuration, making it more concise and maintainable.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Amygos]

@copilot 6061/udp should also be opened

[Copilot]

@copilot 6061/udp should also be opened

Done. Added 6061/udp to match the configuration of port 5061. See commit 992fffb.

[Amygos]

@copilot use the same pattern:

    "5060-5061/tcp",
    "5060-5061/udp",

[Copilot]

@copilot use the same pattern:

    "5060-5061/tcp",

...

Done. Changed to use range pattern 6060-6061/tcp and 6060-6061/udp to match the pattern used for ports 5060-5061. See commit d685c96.