Hello.
I have a link connecting one PBX ( R6.0.1 ) to another ( R3.2 ). Internal calls from one side to the other are working fine.
Sometimes on the second PBX with the old release I get the following incident :
21/02/07 12:47:15 000002M|--/--/-/---|=2:2768=Network mgt : transfer of the file LOG.1.1980 impossible
I don't know what to do about it.
Another thing is that when I want to make changes to the second PBX, I connect through telnet to the second PBX.
Is it possible to have the second PBX users on the first PBX ????
Link between 2 4400 PBX
-
knightr1der
Hey Wizzy,
WOW! 6.0.1 linked to a 3.2 I am not surprised you are seeing the LOG incidents. While the broadcast feature is enabled, the 2 systems will try and update each other with various management changes that have taken place. The error occurs when there are database elements that the other system does not recognise. As you know, there are lots of new elements in 6.0.1 when compared with 3.2
The best way to minimise the amount of errors would be to only broadcast a few things such as phonebook & Entity & perhaps one or two other things. Otherwise don't worry too much about the problem.
As for have the users on one system to manage, why don't you use the tunnel address to allow you to use your 4730/4740?
WOW! 6.0.1 linked to a 3.2 I am not surprised you are seeing the LOG incidents. While the broadcast feature is enabled, the 2 systems will try and update each other with various management changes that have taken place. The error occurs when there are database elements that the other system does not recognise. As you know, there are lots of new elements in 6.0.1 when compared with 3.2
The best way to minimise the amount of errors would be to only broadcast a few things such as phonebook & Entity & perhaps one or two other things. Otherwise don't worry too much about the problem.
As for have the users on one system to manage, why don't you use the tunnel address to allow you to use your 4730/4740?
-
knightr1der
When you say you can only telnet to the remote node, what IP@ are you telneting to?
In any case,
I have a document that explains how to set up 4730/4760 remote management via x25 but I will try and explain here:
In the 4760 PC, define an additional gateway address as the local 4400 tunnel. So if the PC is in the same place as Node 1 then the added gateway address will be 172.30.253.1 (default x25 address)
In the remote 4400, create a static route using netadmin -m as:
Remote Host: 10.1.2.10 (4760 PC address)
Remote gateway: 172.30.253.1
I'm pretty sure thats all you have to do (I have only ever done this once in 6 years) unless I have missed something, in which case please correct me someone.
In any case,
I have a document that explains how to set up 4730/4760 remote management via x25 but I will try and explain here:
In the 4760 PC, define an additional gateway address as the local 4400 tunnel. So if the PC is in the same place as Node 1 then the added gateway address will be 172.30.253.1 (default x25 address)
In the remote 4400, create a static route using netadmin -m as:
Remote Host: 10.1.2.10 (4760 PC address)
Remote gateway: 172.30.253.1
I'm pretty sure thats all you have to do (I have only ever done this once in 6 years) unless I have missed something, in which case please correct me someone.
-
xml
Re: Link between 2 4400 PBX
yes,please verify brodcast setup...wizzy wrote:Hello.
I have a link connecting one PBX ( R6.0.1 ) to another ( R3.2 ). Internal calls from one side to the other are working fine.
Sometimes on the second PBX with the old release I get the following incident :
21/02/07 12:47:15 000002M|--/--/-/---|=2:2768=Network mgt : transfer of the file LOG.1.1980 impossible
I don't know what to do about it.
Another thing is that when I want to make changes to the second PBX, I connect through telnet to the second PBX.
Is it possible to have the second PBX users on the first PBX ????
-
knightr1der
Re: Link between 2 4400 PBX
xml - this thread went to sleep in Feb earlier this year. However, you seem to have just woken up, so, GOOD MORNING 
