Difference between revisions of "WIRES-X"

(→‎Silent call from Fusion operator)
(→‎Limitations)
Line 20: Line 20:
 
=== Limitations ===
 
=== Limitations ===
 
* Room should be run in digital only mode
 
* Room should be run in digital only mode
−
* Room should have static IP and not use UPnP port forwarding (manually forwarded UDP ports or direct connection)
 
−
* Calls from DMR cannot be audited via WIRES-X node or WIRES-X Remote Monitor (call will be silent on this software)
 
 
* 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)
 
* 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)
  

Revision as of 18:50, 28 September 2020

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)
  • WIRES-X directory service (ILS) client can be implemented as external utility
    • D-BUS API to connect rooms including support of rooms behind UPnP NAT
    • WIRES-X directory service client is not in scope of project for now

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 = "<CALL-ND>";
  7.   // Connection profiles
  8.   connections =
  9.   [
  10.     "RoomXXXXX",
  11.     "RoomXXXXX"
  12.   ];  
  13. };
  14.  
  15. RoomXXXXX :
  16. {
  17.   // Room ID: ITALY
  18.   // Group ID
  19.   number = TG number;
  20.   // Remote node address
  21.   address = <"IP ADRESS or Domain Name">;
  22.   // Connection mode:
  23.   // 0 - Regular
  24.   // 1 - Persistent
  25.   mode = 0;
  26. };

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
Retrieved from "https://wiki.brandmeister.network/index.php?title=WIRES-X&oldid=15350"

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 = "<CALL-ND>";
  7.   // Connection profiles
  8.   connections =
  9.   [
  10.     "RoomXXXXX",
  11.     "RoomXXXXX"
  12.   ];  
  13. };
  14.  
  15. RoomXXXXX :
  16. {
  17.   // Room ID: ITALY
  18.   // Group ID
  19.   number = TG number;
  20.   // Remote node address
  21.   address = <"IP ADRESS or Domain Name">;
  22.   // Connection mode:
  23.   // 0 - Regular
  24.   // 1 - Persistent
  25.   mode = 0;
  26. };

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]