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

[sadim]

Hi,
The configuration seems ok.
Can you check the output of the command "sipregister" on the main cpu and on the standby cpu, and compare them.
Can you also show us, the output of "motortrace c"

[sadim]

Sorry,
Can you show also the output of "sipgateway"

[fery_s]

Make sure that both cpu are in Sync. use a new cpu clony and test it again. Also, I recommend updating your patch to the last one, which is j1.410.63.b, if I'm not mistaken. Release 10 had a lot of bugs in SIP.

[aflores]

Hello All. Tanks for yours replies.

Conserning te sugestión of chance de sipconfig file dns2 parameters día not resulta.

Conserning te others sugestiones I will get asap te information requested.

Regards.

AFlores

[aflores]

Hello all. Hope all you are fine.

here there are the fiels with the result of commands sipregister, motortrace c and sipgateway.

From my view, the result in both cpus are the same.

sip register in both cpu shows: registred user number : 669.

Regars

AFlores.

[sadim]

Hi,

It seems to be all OK (assuming that this does not change during the day, due for instance high traffic, ...)
The only thing that i can think of without traces (ip and motortrace traces) is that perhaps, there is an issue at ip level, on the network (eg, convergence time too high, when the main address changes from one CPU to the other).
Can you ask data guys, to check that (perhabs they need to enable fast spanning tree on the ports were the two cpu's are connected).
You can also check that, making a ping from a pc to the main address (10.159.183.51), make a bascul and check how long it takes between the icmp loss from the active cpu, till the icmp is ok again due the answer from the new active cpu (previous standby cpu).

[haroun]

HI Aflores

From my view, the result in both cpus are the same.

sip register in both cpu shows: registred user number : 669.

Regars

AFlores.

Except the delay there's 100 s between registration on both two CPUs, i don't know why? is this normal ?

[haroun]

sip registarion under wireshark or motortrace 3 IF U CAN

[sadim]

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.

[sadim]

Hi,
in one of the sets you can try this alternative configuration:
proxy_addr=10.159.183.52
registrar_addr=10.159.183.52
proxy2_addr=10.159.183.53
registrar2_addr=10.159.183.53
If the set works well with this configuration, then you have a workaround that you can implement in the rest of the sets.