Page 3 of 4

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 22 May 2021 05:27
by sera544
Instead of trying with IP address, try to configure CPU NAME ( FQDN ) and seem failover will work. I remember I did it for some sites.

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 22 May 2021 18:49
by haroun
sadim wrote: 21 May 2021 06:49 Hi,
The 100s difference, should be (and considerenting that booth CPUs have same time) the difference between the date/time when you run the command on one CPU and the date/time of same command on the other CPU.
Hi sadim and thank you for the hint :D

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 22 May 2021 18:52
by haroun
sera544 wrote: 22 May 2021 05:27 Instead of trying with IP address, try to configure CPU NAME ( FQDN ) and seem failover will work. I remember I did it for some sites.
hi but as you see there no reel DNS server in the sip config file the oxe@ip address is used instead,how the oxe will reply for the DNS query ? by only internal name resolve activation ?!

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 23 May 2021 16:37
by sadim
Hi,

You just need to activate via netadmin the Internal name resolver. The OXE will reply to dhs querys on his node name (in your case nodo40)

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 24 May 2021 09:04
by aflores
Hello All.

Thaks for all yours repllies.

Next Wenesday Iwill be on site and will take in consedartion all your suggestions. No matter that I can do some coomands remotly but I can not do any change on sipconfig files since I dont have access to the server wich have the sipconfig files on it.

Here it is attached the result of motor trace 3

regards

AFlores

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 24 May 2021 17:31
by sadim
From the sent trace I don't see anything abnormal. I see a lot of requests and options and their responses.
Are you sure the problem had ocurred on this bascul?
motortrace.png

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 24 May 2021 18:43
by ReverseFlash
Hi guys!
I'ved a some trouble like this... but with PCS, obviously... it's different! but may be it's helpful!:
- The node name and IP address attached declaration wasn't the same, update IPs in PCS.
- on SIP phone's IP Domain the I checked the IP address server declarated.
- In SIPphones I disabled the keepalive mode, and add the IP from the CS and PCS, for me works!, or may be check the DNS's resolve which you use.
- And in other issue similar but with IPphones, the communications it was impossible when I change the Role server, I checked the connection FTP, telnet, etc directly to the IP Role and the IP physic. If you can't to connect it's about some file which resolve the connections.

some suggest!

regards!

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 25 May 2021 09:27
by aflores
Hello Sadim.

Yes I´m sure. Thats the extrange thing, some phone show correctly the date and time but cannnot receive or make internal or extenal call. some others show NOT CONNECTED.
As soon a new bascul is made (to return to cpu_06 as main cpu) all the phones star to work immediately properly without any troubles.

Answering a previous quetion, I have made several mastercopies with the result already know, when cpu_10 is in main role no comunications at all.

As I said before, tomorrow I got authorizacion to be on site so, that it is my planning:

1) Make a complete backup un cpu_6 including Chorus and Linux data.
2) Disconect these App server (cpu_06) from LAN (not need to shutdown -h, Am´I right?)
3) Restore the complete backup on cpu_10 (including Chorus and Linux data) so it will become in: cpu_06 (a clone)
4) Star services on this app server (before cpu_10 and now as cpu_06)
5) See what happens.
6) If, same behavior is present, Will connect the new cpu_06 on the same port of swich an see again what happens.

Thanks to all for your replies.

AFlores

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 25 May 2021 20:14
by haroun
hi Aflorese
looks like issue is in the appliance
any chance that you get a motortrace for an incoming call to one of those sets wich have date & time when cpu6 is main?

Re: SIP user did not connect to the redundant CPU went it is in main role.

Posted: 26 May 2021 14:22
by aflores
haroun wrote: 25 May 2021 20:14 hi Aflorese
looks like issue is in the appliance
any chance that you get a motortrace for an incoming call to one of those sets wich have date & time when cpu6 is main?

Hello, yes I was thinking on that too, that the reason I was going to do some test yesterday but the maintenace window was canceled so it was not possible to do the assitant yesterday. I have to wait until next Wednesday.

I will try to do the test that you suggest and let you know the result.

Regards

AFlores