WIRES-X
Revision as of 18:45, 27 November 2022 by KC0EQA (Talk | contribs) (→‎Configuration)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Starting BrandMeister release 20160421-112227 has support of WIRES-X connectivity.

WIRES-X Link allows:

  • To make bridges between DMR talking groups and WIRES-X rooms
  • Transfer voice calls between BrandMeister Network and WIRES-X network with audio quality 1:1 and signaling conversion

Benefits

  • Fully transparent calls between DMR and WIRES-X
  • Full call signaling support in both directions
  • Sound quality is 1:1 in both directions
  • No extra hardware is required(*)
  • Late call entry is supported on both sides in both directions
  • System Fusion / WIRES-X side doesn’t loose any features
  • Each BrandMeister Server can be connected to several rooms

Conceptual view

BM-WIRES.png

Limitations

  • Room should be run in digital only mode
  • BrandMeister server requires registered node ID and Call-Sign at Yaesu WIRES-X System (these credentials should not be used by any node or you should grant that node with these credentials will never be connected to required rooms)

Additional features

  • CLI-based support of chat for WIRES-X administrators:
    • Incoming messages are available via syslog
    • D-BUS API to send messages
    • Additional CLI utility SendWiresXMessage.php (not supplied to distribution)
  • Two options to connect:
    • Static IP or dynamic DNS
    • WIRES-X directory service (ILS) - implemented as Registry plug-in
  • Built-in support of DN and VW modes

Allocated ports

  • UDP 46110
  • UDP 46112

Configuration

  1. WiresXLink :
  2. {
  3.   // DTMF ID of local node
  4.   number = NODE ID;
  5.   // Call of local node
  6.   call = "<NODE-ND>";
  7.   // DP-ID of local "radio"
  8.   serial = "xxxxx";
  9.   // Connection profiles
  10.   connections =
  11.   [
  12.     "RoomXXXXX",
  13.     "RoomXXXXX"
  14.   ];  
  15. };
  16.  
  17. RoomXXXXX :
  18. {
  19.   // Room ID: ITALY
  20.   // Group ID
  21.   number = TG number;
  22.   // Remote node address
  23.   address = "<IP ADRESS or Domain Name>";
  24.   // Connection mode:
  25.   // 0 - Regular
  26.   // 1 - Persistent
  27.   // 2 - Regular, auto-reconnect on inactivity
  28.   // 3 - Persistent, auto-reconnect on inactivity
  29.   mode = 0;
  30. };

Issues with connectivity

No sound from WIRES-X at all, BM Status web page shows “0 members”

Check your firewall rules, port UDP 46112 should be allowed.

DMR radio (and Last Heard) shows talking group number instead ID of operator

  • Operator has not registered his call-sign in CCS7 registration system - ask him to register
  • 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

  1.   "plugs" :
  2.   {
  3.     "210-FusionDirector" :
  4.     {
  5.       "WiresNodeID" : <ID of registered WIRES-X node>,
  6.       "HRISerial" : "<HRI-200 serial number>"
  7.     }
  8.   }

WiresSubscriptions

  1.   Space WiresSubscriptions:
  2.     1 - BrandMeister Instance ID
  3.     2 - BrandMeister Application ID
  4.     3 - DMR Group ID
  5.     4 - WIRES-X Room ID
  6.  
  7.   box.space.WiresSubscriptions:replace({ 2621, 262100, 262100, 24007 })
Retrieved from "https://wiki.brandmeister.network/index.php?title=WIRES-X&oldid=18734"

Starting BrandMeister release 20160421-112227 has support of WIRES-X connectivity.

WIRES-X Link allows:

Benefits[edit]

Conceptual view[edit]

BM-WIRES.png

Limitations[edit]

Additional features[edit]

Allocated ports[edit]

Configuration[edit]

  1. WiresXLink :
  2. {
  3.   // DTMF ID of local node
  4.   number = NODE ID;
  5.   // Call of local node
  6.   call = "<NODE-ND>";
  7.   // DP-ID of local "radio"
  8.   serial = "xxxxx";
  9.   // Connection profiles
  10.   connections =
  11.   [
  12.     "RoomXXXXX",
  13.     "RoomXXXXX"
  14.   ];  
  15. };
  16.  
  17. RoomXXXXX :
  18. {
  19.   // Room ID: ITALY
  20.   // Group ID
  21.   number = TG number;
  22.   // Remote node address
  23.   address = "<IP ADRESS or Domain Name>";
  24.   // Connection mode:
  25.   // 0 - Regular
  26.   // 1 - Persistent
  27.   // 2 - Regular, auto-reconnect on inactivity
  28.   // 3 - Persistent, auto-reconnect on inactivity
  29.   mode = 0;
  30. };

Issues with connectivity[edit]

No sound from WIRES-X at all, BM Status web page shows “0 members”[edit]

Check your firewall rules, port UDP 46112 should be allowed.

DMR radio (and Last Heard) shows talking group number instead ID of operator[edit]

Autodiscovery[edit]

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[edit]

  1.   "plugs" :
  2.   {
  3.     "210-FusionDirector" :
  4.     {
  5.       "WiresNodeID" : <ID of registered WIRES-X node>,
  6.       "HRISerial" : "<HRI-200 serial number>"
  7.     }
  8.   }

WiresSubscriptions[edit]

  1.   Space WiresSubscriptions:
  2.     1 - BrandMeister Instance ID
  3.     2 - BrandMeister Application ID
  4.     3 - DMR Group ID
  5.     4 - WIRES-X Room ID
  6.  
  7.   box.space.WiresSubscriptions:replace({ 2621, 262100, 262100, 24007 })