Author Topic: RPT1 and RPT2 callsign  (Read 1611 times)

KU4HP

  • Posts: 1
RPT1 and RPT2 callsign
« on: September 18, 2009, 06:28:59 PM »
When using a DStar repeater for local communications do the RPT1 and RPT2 callsign have to match the repeater I am attempting to us.  For example could I connect to a repeater say in Colorado (if I were close to the repeater) with the callsigns for RPT1 and RPT2 set to say a repeater in Georgia.  This is assuming that the correct frequency is being used for the Colorado repeater. 

If the RPT1 and RPT2 don't have to match the source repeater then why have them in the radio?

n5ebw

  • Administrator
  • *****
  • Posts: 112
Re: RPT1 and RPT2 callsign
« Reply #1 on: September 18, 2009, 08:58:06 PM »
Yes, they have to match the repeater you are using.  You cannot connect to the local repeater with the Georgia callsign, as it will omit your traffic (this is a function of the D-Star repeater controller).  Someone might hear you on simplex (on the repeater receive frequency), but the controller itself will drop your traffic.  RPT1 is the source repeater with node and RPT2 is the gateway node.  URCALL is the destination.  RPT1 and 2 always have to match the repeater you are using locally.

For local traffic, you can omit RPT2, but we (D-Starusers.org) would like it if the G node designation of the repeater you are using stays in RPT2, it harms nothing, and helps us do the last heard accounting where Dstarmonitor is installed.

We must free ourselves of the hope that the sea will ever rest. We must learn to sail in high winds. --Aristotle Onassis