Breggen
Newbie
I am trying to connect KAS-10 over IP-Conventional to the repeater. I have two computers I am trying this with.
1. The gateway computer ( 172.20.11.1 ) that is connected directly to the repeater ( 172.20.11.11 )
2. A remote computer that is on the other side of the VPN tunnel
Keep in mind that both computers are able to read/write the repeater config through KPG-129D.
On both computers I installed a test version of KAS-10. Both configured to use NXDN over IP-Conventional. The gateway has the 172.20.11.1 as interface to work on, the other the VPN interface. On has ID 2000 and the other 2001. Both numbers are in the IP-Console tab of the configuration of the repeater. Both IP addresses are in the network and are connected as being one site.
Now both installations of KAS-10 give "Standby 2000" in there console status window. And in the status bar the IP address of the repeater has a green sphere in front of it and says "Active" as state.
All well you should think. But when I key-up my portable, nothing is shown in the activity window. Als when I try to send a message to the portable from KAS-10 I get a message that there is a communication error with the repeater.
Not being one to give up easily, I started wireshark and looked at the packets going round to the repeater and back. I see an UDP SIP request being made when I hit the "send" button in KAS-10 to transmit the message. But the repeater reacts with a "403 Forbidden" as answer. Well now I am puzzled, is there some form of authentication needed for this? I searched around in either KAS-10 and KPG-129. The only "encryption" type thing I can find is the "Encryption type" which is 1 on both sides.
I also added the IP-addresses of the KAS-10 to the IP-conventional site-group of the channel I am using. When I did this i saw a lot of UDP packages comming in the moment i keyed up my portable, but KAS-10 still doesn't show anything in the activity window. Nor can i send a message.
It doesn't seem to be a UDP routing problem or something like that because i can see it communicate forth and back, and KPG-129 works. But does anybody have any ID why KAS-10 is not showing anything in the activitylog and rejects SIP requests?
With regards,
Michel van der Breggen
1. The gateway computer ( 172.20.11.1 ) that is connected directly to the repeater ( 172.20.11.11 )
2. A remote computer that is on the other side of the VPN tunnel
Keep in mind that both computers are able to read/write the repeater config through KPG-129D.
On both computers I installed a test version of KAS-10. Both configured to use NXDN over IP-Conventional. The gateway has the 172.20.11.1 as interface to work on, the other the VPN interface. On has ID 2000 and the other 2001. Both numbers are in the IP-Console tab of the configuration of the repeater. Both IP addresses are in the network and are connected as being one site.
Now both installations of KAS-10 give "Standby 2000" in there console status window. And in the status bar the IP address of the repeater has a green sphere in front of it and says "Active" as state.
All well you should think. But when I key-up my portable, nothing is shown in the activity window. Als when I try to send a message to the portable from KAS-10 I get a message that there is a communication error with the repeater.
Not being one to give up easily, I started wireshark and looked at the packets going round to the repeater and back. I see an UDP SIP request being made when I hit the "send" button in KAS-10 to transmit the message. But the repeater reacts with a "403 Forbidden" as answer. Well now I am puzzled, is there some form of authentication needed for this? I searched around in either KAS-10 and KPG-129. The only "encryption" type thing I can find is the "Encryption type" which is 1 on both sides.
I also added the IP-addresses of the KAS-10 to the IP-conventional site-group of the channel I am using. When I did this i saw a lot of UDP packages comming in the moment i keyed up my portable, but KAS-10 still doesn't show anything in the activity window. Nor can i send a message.
It doesn't seem to be a UDP routing problem or something like that because i can see it communicate forth and back, and KPG-129 works. But does anybody have any ID why KAS-10 is not showing anything in the activitylog and rejects SIP requests?
With regards,
Michel van der Breggen