Alcatel Unleashed

I have an OXE R11.1 with 3 SIP trunks.
TG90(Local gateway),TG91(external gateway 1) and TG99(ARS 93 Route 1).
All trunks are working fine.

TG 99 has 20 Access numbers, delete TG99 and rebuild ,Access numbers is set to 2.
TG 99 remains in HS stat, Unable to check the status of TG 90 and 91.
TG 99 Access number changed back to the original 20.
TG 99,91 and 90 remains in HS state.

I want to delete all SIP Trunks and rebuild them
Through a series of actions, such as the sunnetwork and TG of the local sip gateway are set to -1, deleting the SIP external gateway, deleting the ARS 93 Route 1……, only Trunk 99 cannot be deleted

The access number of Trunk 99 is duplicated, and the access numbers of Trunk 99 of CPU A and CPU B are different, as follow
CPU A TG99 Nb Access 1-10：75-74,73-75,70-69,68-67,66-65,64-63,62-61,60-59,58-57,74-54
CPU b TG99 Nb Access 1-10：73-72,71-73,69-68,67-66,65-64,63-62,61-60,59-58,57-56,72-54
Shutdown CPU A after shutting down CPU B, the TG99 access number of CPU A and B becomes the same, but TG99 still has duplicate TG Number 72 and 73, as follow
CPU A and B TG99 Nb Access 1-10：73-72,71-73,69-68,67-66,65-64,63-62,61-60,59-58,57-56,72-54

Still cannot delete TG99, SIP trunk still does not work

Does anyone have some suggestions???

Why for you interesting TG access numbers (for SIP TG)?
Cannot delete - describe, PBX give you some reason during reject, share it with us...

I am kevin770571
forget password
Sign in with another account-kevin24257078

An error message [Error: Press cancel to remove this window operation] appears about 1 minute after executing the delete TG command.
Before the error message appears, use another connection to see that TG99 is gone. After the error message appears, TG99 appears again.

TG 99 has 20 Access, Number of trunk should be 620
But querying the status of TG 99, there are only 558 Number of trunks, and the reduction of 62 Trunks seems to be caused by the duplication of 2 TG Access Numbers
In this case, I think TG cannot be deleted because TG Access Number is duplicated

I have another OXE, delete 1 SIP Trunk and cause SIP service interruption
Delete and rebuild all SIP trunk and External Gateway, and the service returns to normal.
So try to delete all TG




Today, TG90 and 91 are newly established, Access Nb is set to 2, and the status of TG90 and 91 is hs
TG90 and 91 Access Nb increase to 4, TG90 and 91 cannot query trunk status
The status of TG99 also changes, and the Number of Trunk of TG99 changes from 558 to 682
And the state of CPU A and CPU B are different
The related logs of CPU A and CPU B are attached

The problematic OXE execute netstat -an | grep LISTEN instruction as follows
(1)xa000000> netstat -an | grep LISTEN
tcp 0 0 0.0.0.0:514 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5060 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2565 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2533 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2535 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:2569 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2539 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2540 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2555 0.0.0.0:* LISTEN


Normal OXE execute netstat -an | grep LISTEN instruction as follows
(1)xa0r0600> netstat -an | grep LISTEN
tcp 0 0 0.0.0.0:514 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5060 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5540 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2565 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2533 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2535 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:2569 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2539 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2540 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2555 0.0.0.0:* LISTEN


The problematic OXE is missing port 5540, why?
How to fix it?

Is it related to the inability to delete SIP TG?
Is it related to abnormal SIP service?

Don't mess with the ports it would lead you nowhere.
Shut down the stand-by CPU or just disable telephony autostart on Stand-By and reboot.
Make all necessary configuration on Main CPU - delete, create or modify - all that you think should be done with the SIP TG.

After all is done check whther it works. If yes - just put stand-by CPU back in service via swinst menu(with DB duplication etc).

Hi, Alex

Thank you for your reply

Last Wednesday: All other SIP-related components except TG99 were deleted. After the SIP-related components were created, the newly created TG would not work, and then restart CPU A and CPU B(only one CPU is shutdown at the same time), the newly created TG would also not work

Last Friday: All other SIP-related components except TG99 were deleted. Restart CPU A and restart CPU B. Make CPU data clean (only one CPU is shutdown at the same time). TG99 still cannot be deleted

This Monday: In the case of last Friday, the establishment of TG90, SIP gateway and External SIP Gateway, can make calls through SIP TG90

The problem of TG99 data disorder may be solved by turning off CPU A and B at the same time as Alex said
But it will affect more than 1,000 analogies and digital users, I will find the one that affects the user with the least time to execute, try it out

Hi Kevin were you able to delete the SIP trunk? I am facing similar problem in rel 12.2.