Thanks for the reply, Jim.

>>“You didnt change the IAX2 port number in the portal”

Yes I did! In fact, it was the first thing that I did (step 1 below).

I’ve just been back to the portal to check and the entry for server “Test” says “UDP Port:4568” and 2484 is associated with server “Test”. I also verified that server “Bride” (2481, which is on the same public IP) was correctly set-up, and it is.

[Screenshot here]

It still appears to be an issue that there are two entries for the same node (2484) in the rpt_extnodes file. Surely, for a given node number, there should only ever be one?

When I restart Asterisk, I get this message - amongst others - which suggests that I at least got that bit right.

-- Registered IAX2 to '67.215.233.178', who sees us as 89.107.6.110:4568 with no messages waiting

As an experiment, I deleted both lines for 2484 from rpt_extnodes. Within two minutes they were back!

Is it possible that the central database still holds an entry for 2484 from before the change, and that it hasn’t been scrubbed / updated?

I have stopped Asterisk on “Test” for now to see what happens when it drops “off the radar”.

Scratchy head time J

David

From: Jim Duuuude [mailto:telesistant@hotmail.com]
Sent: 03 October 2010 13:52
To: david.osborn@manx.net; app_rpt mailing list
Subject: RE: [App_rpt-users] Changing Node Numbers

You didnt change the IAX2 port number in the portal. It really needs to know
the accurate info. Look at the Server under the Network Configuration Tab.
Change the UDP port to whatever you made it. This will help immensely.

JIM

> From: david.osborn@manx.net
> To: app_rpt-users@qrvc.com
> Date: Sun, 3 Oct 2010 13:09:02 +0100
> Subject: [App_rpt-users] Changing Node Numbers
>
> Hi,
>
> I have just followed Jim's instructions to change a node's port number.
>
> 1. Visit the portal and change the number there.
> 2. Edited IAX.Conf and restarted.
>
> This is a test node that is co-sited with node 2481 on port 4569 - hence the
> need for another port.
>
> When I attempted to connect to the node (2484) from the web transceiver, the
> call failed. Looking at the console for 2484 showed no incoming activity, it
> turned out that the call was being directed to node 2481 on port 4569; the
> Web Transceiver was using the old port number.
>
> I attempted to connect to 2484 from another node and that also failed. It
> transpired that rpt_extnodes had now got two entries for 2484. Here's an
> extract from the file:
>
> 2480=radio@87.254.94.29:4568/2480,87.254.94.29
> 2481=radio@89.107.6.110:4569/2481,89.107.6.110
> 2482=radio@87.254.94.29:4569/2482,87.254.94.29
> 2483=radio@217.28.14.128:4569/2483,217.28.14.128
> 2484=radio@89.107.6.110:4569/2484,89.107.6.110
> 2484=radio@89.107.6.110:4568/2484,89.107.6.110
> 2490=radio@68.227.84.117:4569/2490,68.227.84.117
>
> This extract was taken more than an hour after making the portal changes.
>
> Is this a problem with the node list updates, or have I missed something?
>
> Incidentally, I manually corrected the list and the call succeeded straight
> off the bat.
>
> Another, somewhat unrelated thing....
>
> I instructed the portal to download the configuration to the server - it
> didn't! What am I missing here? I have run the scripts on the support page,
> which did the first-time download, but nothing since.
>
> David
> GD4HOZ
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users@qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users