nb
Support Team
- Joined
- Jun 7, 2007
- Messages
- 2,510
- Reaction score
- 392
Ok perfect. thanks for updating us.
Yes you are correct - an IP on it's own does not work in networking. The basic concept of networking is a socket which is an IP and a port. Everything works with ip and ports.
So to continue on what we were discussing earlier (when we were blaming 3CX and considering moving to another pbx), whatever other pbx you use, if it is network based, has to inherit the same networking concepts.
So here we fall back to the Supported and Not supported devices.
You can use a not supported device - but you are on your own to configure them. If you do not look at a configuration and you do not see that without a port this is not going to work, it means that you should check the manufacturer's manual or go for a supported device because thats the benefit of a supported device - it works out of the box because in this example, the port is handled in the template.
Yes you are correct - an IP on it's own does not work in networking. The basic concept of networking is a socket which is an IP and a port. Everything works with ip and ports.
So to continue on what we were discussing earlier (when we were blaming 3CX and considering moving to another pbx), whatever other pbx you use, if it is network based, has to inherit the same networking concepts.
So here we fall back to the Supported and Not supported devices.
You can use a not supported device - but you are on your own to configure them. If you do not look at a configuration and you do not see that without a port this is not going to work, it means that you should check the manufacturer's manual or go for a supported device because thats the benefit of a supported device - it works out of the box because in this example, the port is handled in the template.