(→Additional features) |
(→Configuration) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 43: | Line 43: | ||
number = NODE ID; | number = NODE ID; | ||
// Call of local node | // Call of local node | ||
− | call = "< | + | call = "<NODE-ND>"; |
// DP-ID of local "radio" | // DP-ID of local "radio" | ||
serial = "xxxxx"; | serial = "xxxxx"; | ||
Line 60: | Line 60: | ||
number = TG number; | number = TG number; | ||
// Remote node address | // Remote node address | ||
− | address = | + | address = "<IP ADRESS or Domain Name>"; |
// Connection mode: | // Connection mode: | ||
// 0 - Regular | // 0 - Regular | ||
Line 78: | Line 78: | ||
* Operator has not registered his call-sign in CCS7 registration system - ask him to register | * Operator has not registered his call-sign in CCS7 registration system - ask him to register | ||
* CRC check failed during processing of SystemFusion | * CRC check failed during processing of SystemFusion | ||
+ | |||
+ | === Autodiscovery === | ||
+ | |||
+ | Autodiscovery mode is an alternative mode to connect to WIRES-X rooms. In that mode there is no need to configure profiles in main configuration file. Instead of it the system connects to Yaesu's WIRES-X directory servers and track the changes. '''To use this mode you have to have an WIRES-X node ID from Yaesu and HRI-200 serial number. There numbers should never be used by another connected WIRES-X node.''' | ||
+ | |||
+ | ==== Registry.json ==== | ||
+ | |||
+ | <pre> | ||
+ | "plugs" : | ||
+ | { | ||
+ | "210-FusionDirector" : | ||
+ | { | ||
+ | "WiresNodeID" : <ID of registered WIRES-X node>, | ||
+ | "HRISerial" : "<HRI-200 serial number>" | ||
+ | } | ||
+ | } | ||
+ | </pre> | ||
+ | |||
+ | ==== WiresSubscriptions ==== | ||
+ | <pre> | ||
+ | Space WiresSubscriptions: | ||
+ | 1 - BrandMeister Instance ID | ||
+ | 2 - BrandMeister Application ID | ||
+ | 3 - DMR Group ID | ||
+ | 4 - WIRES-X Room ID | ||
+ | |||
+ | box.space.WiresSubscriptions:replace({ 2621, 262100, 262100, 24007 }) | ||
+ | </pre> | ||
[[Category:Protocol]] | [[Category:Protocol]] | ||
[[Category:Supported protocol]] | [[Category:Supported protocol]] |
Starting BrandMeister release 20160421-112227 has support of WIRES-X connectivity.
WIRES-X Link allows:
WiresXLink : { // DTMF ID of local node number = NODE ID; // Call of local node call = "<NODE-ND>"; // DP-ID of local "radio" serial = "xxxxx"; // Connection profiles connections = [ "RoomXXXXX", "RoomXXXXX" ]; }; RoomXXXXX : { // Room ID: ITALY // Group ID number = TG number; // Remote node address address = "<IP ADRESS or Domain Name>"; // Connection mode: // 0 - Regular // 1 - Persistent // 2 - Regular, auto-reconnect on inactivity // 3 - Persistent, auto-reconnect on inactivity mode = 0; };
Check your firewall rules, port UDP 46112 should be allowed.
Autodiscovery mode is an alternative mode to connect to WIRES-X rooms. In that mode there is no need to configure profiles in main configuration file. Instead of it the system connects to Yaesu's WIRES-X directory servers and track the changes. To use this mode you have to have an WIRES-X node ID from Yaesu and HRI-200 serial number. There numbers should never be used by another connected WIRES-X node.
"plugs" : { "210-FusionDirector" : { "WiresNodeID" : <ID of registered WIRES-X node>, "HRISerial" : "<HRI-200 serial number>" } }
Space WiresSubscriptions: 1 - BrandMeister Instance ID 2 - BrandMeister Application ID 3 - DMR Group ID 4 - WIRES-X Room ID box.space.WiresSubscriptions:replace({ 2621, 262100, 262100, 24007 })
Starting BrandMeister release 20160421-112227 has support of WIRES-X connectivity.
WIRES-X Link allows:
WiresXLink : { // DTMF ID of local node number = NODE ID; // Call of local node call = "<CALL-ND>"; // DP-ID of local "radio" serial = "xxxxx"; // Connection profiles connections = [ "RoomXXXXX", "RoomXXXXX" ]; }; RoomXXXXX : { // Room ID: ITALY // Group ID number = TG number; // Remote node address address = <"IP ADRESS or Domain Name">; // Connection mode: // 0 - Regular // 1 - Persistent // 2 - Regular, auto-reconnect on inactivity // 3 - Persistent, auto-reconnect on inactivity mode = 0; };
Check your firewall rules, port UDP 46112 should be allowed.