IP Repeater Programming

IP Repeater Programming allows a system administrator to program and upgrade repeaters within the system utilizing the IP network. This feature is supported on repeaters equipped with 32MB memory and firmware version R01.07.00 or later. Note that all repeaters in the system must be on the same firmware version as the Master.

Connecting the Customer Programming Software (CPS) to an IP network allows the CPS to
access all repeaters in a Single Site; IP Site Connect; Capacity Plus or Linked Capacity Plus system, utilizing their backend IP network connections.

Prior to using IP Repeater Programming, the feature must be enabled in the repeater, locally connected via USB to the CPS application. The CPS can also communicate with repeaters in analogue mode. The primary requirement is that the repeater must be on an IP network and communicating with a Master repeater. The CPS can only connect to one Master at a time and can only program a single repeater at a time.

Once the repeater has been properly configured and installed in a networked configuration, the CPS needs to know the IP address of either the Master repeater or the router to which the repeater is attached – depending on whether the CPS is within the same subnet as the Master. The CPS then learns the addresses of other repeaters connected to the Master (the same way the Peers do) once the application connects to the Master.

Unlike repeater-to-repeater communication, the CPS application may require firewall configuration. This is to allow the repeater to make a secure connection to the CPS application on the PC. If the PC resides behind a firewall, the firewall will need to be configured to allow inbound traffic (repeater-to-CPS) on a specific CPS TCP port that is configurable in the application.

If the CPS application is connected to the internet, or to the MOTOTRBO network via a router, the Router between the Master and WAN must be configured to forward traffic on specific TCP/UDP ports to the Master repeater. The Master, as well as the WAN port on the router, will need to have a static IP address.
IP Remote Programming CPS configuration (click to enlarge)

Upon initiating an IP Repeater Programming action, the CPS communicates its opened TCP port number to which the repeater attempts to connect. If multiple CPS applications (different PCs) are behind a single firewall, each application must use a unique TCP port number, and the firewall must be configured to correctly route TCP traffic to the corresponding application.

Using the CPS and IP Repeater Programming to provision a repeater will temporarily disable it until the operation is completed. The duration depends on the network bandwidth and amount of data that is transferred to complete the chosen operation.

It of course makes good sense to enable codeplug password authentication on a per repeater basis and can be provisioned in the repeater prior to using this feature.


  1. So if the CPS PC was behind the same router as the Master repeater (see above diagram), then the Master IP address in the CPS IP system settings would be the same as the repeaters' ethernet IP address -

    If the CPS PC was on another LAN or on the WWW, then the CPS Master IP address would be set to the WAN IP address of the router used on the Master repeater site -

  2. Hi!

    Given that, if I read this post before, I would not have gone mad, to use CPS remotely! I think, for newbie, it is better to emphasize the step where you need a port NAT on router/firewall to allow incoming traffic from remote repeater to the CPS. Having said that, I would say that something should be added on a couple of error messages.

    Error 5456:

    The connection request from the repeater does not happen, check the settings of the router, firewall, and PC! All must allow incoming TCP traffic to the port you choose to communicate (TCP Port CPS). In particular, check that you have set the port forwarding on the router, example on Cisco router:

    ip nat inside source static tcp 50010 50010 extendable

    where is the IP address of the PC that is running CPS, 50010 is the TCP port chosen in the configuration and is the public address of the router.

    Error 5818:

    An earlier request to connect to the repeater has gone wrong in the initial phase and the repeater does not allow to enter with another session. In this case it is sufficient to reboot the repeater to reset the state of that and try to connect again.

    Now this info is not complete, so I do not know if you, Wayne,'d like to add more!


    1. Thanks for the information. I cant think of anything to add at the moment.

      Ciao :-)

  3. Hello ,I have 3 LCP sites with each one repeater, i can program the master but not the peers.The peers appear in the list but when trying to read a connection can not be established.
    Any idea how this is possible

    1. Confirm that the above TCP port (screenshot: top left) is correct and is being passed to/from the repeaters.

  4. Hello MR.WAYANE
    I'm trying to programing my master repeater remotely... I'm using direct connection between my pc and my repeater....
    How can i get the CPS TCP PORT.

    1. You would choose this yourself. The CPS announces this to the repeater.

      Generally the range between 49152 and 65535 is used to not interfere with known (registered) services below it.

  5. Hello MR.WAYANE
    I have 3 SLR 5500, 1 master with dynamic wan ip, and 2 peers allso dynamic wan ip.
    What be right configuration for ip programing , now I get only error 8499 when I try connect remotly!


  6. Hi Wayne,

    I have 4 x DR3000 in IPSC system. I am able to read/write to all the repeaters through IP and I have successfully updated the firmware in one of the repeaters, also through IP. However, when I try to update the FW in the remaining 3 repeaters everything works fine until 82% and then I get error #8395 "Application has encountered an error. The device response was not received within the allotted time." After this error code if I try reading the repeater again I get error #8661 "Port conflict in the local machine", until I close and re-open CPS then I can read/write normally again (until I try update FW again). I have tried resetting the PC, and all 3 repeaters but it still always fails FW update on 82%, can you think why?

    Also now that I am running the system with repeaters on different FW, I know it is advised against but what could go wrong? It seems to work without problems.


    1. Which firmware are you upgrading from and to? It maybe that you are trying to upgrade from a very old to the latest version.

      There could be a problem with port forwarding on the access routers: specifically the CPS TCP and UDP ports.

      That's all I can think of. Otherwise a look at whats happening with WireShark might provide some clues...

    2. I'm upgrading from R02.40.01 to R02.08.05.03 (latest version). This makes a lot of sense as the repeater that updated successfully was running R.02.40.20 (just slightly later than the others). If this is indeed the problem then how many FW versions do I need to install? And which ones? Would my dealer be able to get older versions of FW for me?

      Could it be that there is a problem with the port forwarding yet I am still able to read/write the repeater, just not update FW?

      Thanks for your help as always!


  7. This comment has been removed by a blog administrator.

  8. This comment has been removed by the author.

  9. Bom dia WAYNE HOLMES, para esse tipo de programação eu tenho que ativar alguma licença no CPS?

  10. Bom dia WAYNE HOLMES, para esse tipo de programação eu tenho que ativar alguma licença no CPS?

  11. Good morning WAYNE HOLMES, for special programming I have to activate some non-CPS license?

    1. It depends on what you mean by special programming? And which region you are in...

  12. I have Connect plus system and want to upgrade firmware on repeaters. My RRP port is 38001 and CPS id is 20. I can connect to remote system and read list of repeaters connected to XRC. but when trying to read repeater i get error #9353. Tried different CPS TCP and UDP ports.

    1. I don’t know what that error code means (the error codes don’t point to a specific problem in ant case).

      Some detective work is needed:
      Set the CPS TCP port to 50000. Try reading the Repeater and using WireShark to see whether this traffic is arriving at the various points between the PC and repeater. The point at which the traffic is not seen is where it’s lost.


Powered by Blogger.