# Connecting different two nodes, issued to two different call signs not able to connect to each other , but will connect to other nodes with no issue

**URL:** <https://community.allstarlink.org/t/connecting-different-two-nodes-issued-to-two-different-call-signs-not-able-to-connect-to-each-other-but-will-connect-to-other-nodes-with-no-issue/18836>\
**Category:** AllStarLink\
**Created:** [August 27, 2021, 5:55pm UTC](https://community.allstarlink.org/t/connecting-different-two-nodes-issued-to-two-different-call-signs-not-able-to-connect-to-each-other-but-will-connect-to-other-nodes-with-no-issue/18836 "2021-08-27T17:55:22Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![nolyn78](https://community.allstarlink.org/user_avatar/community.allstarlink.org/nolyn78/32/1860_2.png) [@nolyn78](https://community.allstarlink.org/u/nolyn78)\
**Post date:** [August 27, 2021, 5:55pm UTC](https://community.allstarlink.org/t/connecting-different-two-nodes-issued-to-two-different-call-signs-not-able-to-connect-to-each-other-but-will-connect-to-other-nodes-with-no-issue/18836/1 "2021-08-27T17:55:23Z")

</div>

I have set up two different RPI 3, with two different nodes issue to two different callsigns. If I connect the first node to another node, no issue. If I connect the 2nd node to another node, no issue. But if I connect both nodes together, it will not connect. Please advise.

---

<div class="post-metadata">

**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\
**Post date:** [August 27, 2021, 8:04pm UTC](https://community.allstarlink.org/t/connecting-different-two-nodes-issued-to-two-different-call-signs-not-able-to-connect-to-each-other-but-will-connect-to-other-nodes-with-no-issue/18836/2 "2021-08-27T20:04:07Z")

</div>

AllStar nodes connect by the node number not the by callsign. Think telephone system: phones connect by the number not the persons name.

When there is more than one server behind a NAT router, each node must have it own port. Please take a look at this:

[https://wiki.allstarlink.org/wiki/Two\_Servers\_Behind\_NAT\_Router](https://wiki.allstarlink.org/wiki/Two_Servers_Behind_NAT_Router)

Please configure your node per the PDF.

---

<div class="post-metadata">

**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\
**Post date:** [August 28, 2021, 3:39am UTC](https://community.allstarlink.org/t/connecting-different-two-nodes-issued-to-two-different-call-signs-not-able-to-connect-to-each-other-but-will-connect-to-other-nodes-with-no-issue/18836/3 "2021-08-28T03:39:24Z")

</div>

If both nodes are on the same network router (NAT), and not under the same server (computer), you will need to specify the full ‘LOCAL’ connection/port to the other node via rpt.conf under ‘nodes’

48233 = radio@192.168.1.123:4569/48233,NONE

additional…  
If both nodes have also a private node (ie 1999) connected of the same number, a automatic loop-back prevention will block the attempted connection.  
The quick fix is to use a more obscure node numbers for private nodes (ie 1441)

---

<div class="post-metadata">

**Author:** ![nolyn78](https://community.allstarlink.org/user_avatar/community.allstarlink.org/nolyn78/32/1860_2.png) [@nolyn78](https://community.allstarlink.org/u/nolyn78)\
**Post date:** [August 29, 2021, 5:34pm UTC](https://community.allstarlink.org/t/connecting-different-two-nodes-issued-to-two-different-call-signs-not-able-to-connect-to-each-other-but-will-connect-to-other-nodes-with-no-issue/18836/4 "2021-08-29T17:34:38Z")

</div>

HI Tim and Mike,  
Thak you so much for the information. Just got busy to reply. I appreciated all the assistance and both systems are currently working fine. Thank you very much.

---

<div class="post-metadata">

**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\
**Post date:** [August 29, 2021, 9:37pm UTC](https://community.allstarlink.org/t/connecting-different-two-nodes-issued-to-two-different-call-signs-not-able-to-connect-to-each-other-but-will-connect-to-other-nodes-with-no-issue/18836/5 "2021-08-29T21:37:58Z")

</div>

So, for the benefit of others, what did you find to correct the issue.

---

<div class="post-metadata">

**Author:** ![nolyn78](https://community.allstarlink.org/user_avatar/community.allstarlink.org/nolyn78/32/1860_2.png) [@nolyn78](https://community.allstarlink.org/u/nolyn78)\
**Post date:** [August 30, 2021, 1:36am UTC](https://community.allstarlink.org/t/connecting-different-two-nodes-issued-to-two-different-call-signs-not-able-to-connect-to-each-other-but-will-connect-to-other-nodes-with-no-issue/18836/6 "2021-08-30T01:36:02Z")

</div>

Hello Mike,  
I followed your instruction of specifying you provided with assigned different port. Make sure you open the port at the router.  
For A Node at the rpt.conf:  
XXXXA = radio@127.0.0.1:4569/XXXXA,NONE  
XXXXB = radio@192.168.1.123:4568/XXXXB,NONE

For B Node at the rpt.conf:  
XXXXB = radio@127.0.0.1:4568/XXXXB,NONE  
XXXXA = radio@192.168.1.120:4569/XXXXA,NONE

This solved the issue. it is working fine.

---

<div class="post-metadata">

**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\
**Post date:** [September 2, 2021, 1:36am UTC](https://community.allstarlink.org/t/connecting-different-two-nodes-issued-to-two-different-call-signs-not-able-to-connect-to-each-other-but-will-connect-to-other-nodes-with-no-issue/18836/7 "2021-09-02T01:36:15Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
