@Col_H 

1. Firmware of your product.

2. To verify the inbound, you can only use the Wireshark to mirror the port and monitor that. All router interfaces cannot display the information like inbound and outbound traffic. 

If you have done Wireshark, you can paste the result of the VOIP part about your ISP reply. 

3. What is required to be filled on your GUI and per your ISP? Can you mark them out on a screenshot of your config?

Please mosaic your sensitive information. Here is a list of information considered sensitive:

1. Public IP address on your WAN if your WAN is.

2. Real MAC address of your device.

3. Your personal information including address, domain name, and credentials.

For troubleshooting purposes, when a WAN IP is needed, please leave some values visible for identification.

 @Col_H 

I forgot about mirroring port, anyway, within the router it has pre-defined VOIP providers and I opened up a trail account with one of these and all works ok. The onboard ports work ok, so hardwire ok.

What I realise now, is lots of these VOIP providers maybe use a 3rd party to set up these plug in adapters and do not really know and/or have access to the settings needed if you use your own router or VOIP phone. I do not want to really use one of these.

So I am awaiting the original provider to provide the registration information as clearly the information given does not work.

Will later submit some screen dumps of required information just for clarity.

Thanks

  @Col_H

All ok as seen, on line

I think the Auth ID and Password being supplied is wrong. What I can do later is use wireshark and see if I can see a code number for reason of failure to register, (if its viewable).

I will assume for second registar and SIP server info is correct. However what is interetsing the standard port number is not being used.

Will update later

Now hit a problem, when I use the drop down box for Voiphone it all works.

When I enter the input data manually, it will not register, any ideas?

See below, taken some tags out and rest been randomlly trying. This is other.

 This is VOIPhone drop down 

When I put in data it works

Any thoughts?

Thanks

  Hi @Clive_A 

I resolved it last night, basically various VOIP providers vary their registration hand-shaking. I found this by chance on TP link web find, anyway the registrar ID is used twice and the phone number is omitted. 

I was a bit skeptical but it does go online and all ok. If you delete either the duplicated registrar ID then it fails. I would like to understand why this is the case, but it appears its a common problem but you have to know where to look. Thats the crazy bit as its like knowing the answer but not the question. So the phone number is not passed in the handshake, which i guess makes sense as it could be referenced in a data base else where.

So it all works, at the moment, butr left in  dark as to the protocol whys

  @Col_H 

Col_H wrote

  Hi @Clive_A 

 

I resolved it last night, basically various VOIP providers vary their registration hand-shaking. I found this by chance on TP link web find, anyway the registrar ID is used twice and the phone number is omitted. 

 

I was a bit skeptical but it does go online and all ok. If you delete either the duplicated registrar ID then it fails. I would like to understand why this is the case, but it appears its a common problem but you have to know where to look. Thats the crazy bit as its like knowing the answer but not the question. So the phone number is not passed in the handshake, which i guess makes sense as it could be referenced in a data base else where.

 

So it all works, at the moment, butr left in  dark as to the protocol whys

 

Register ID, you mean the Authentication ID or the Phone number?