SIP Failed for OXE and Avaya IPO 500

[kimy]

Hi there,

Good Day!

A newbie here. Would somebody be please so kind to help me assess what's going on with my SIP trunking between my ALcatel OXE and AVaya IPO 500 v2. Trunks work so fine before when suddenly nor can receive or make calls to each other. Upon checking on both PABX config wise are all the same with its TG, SIP gateway and SIP ext. Gateway when it was still all working fine. Both are also reachable when pinged.
Many thanks!

[vad]

Topic moved in OXE section.
For OXE side at least (if not described management) - explain behavior:
- do you have another SIP connection from OXE (SIP works or not), or you just declare SIP parameters first time without PBX reset.
- what do you have during dialing (on IP/digital set display).
- do you have some incidents related SIP.

[kimy]

@vad

Thanks for replying
So far, we only have oxe to avaya, and yes those are just SIP parameters being checked!Haven't tried PBX reset before.
It says Request Terminated when dialling.

[vad]

After some modification (first time management) - you need to restart PBX. After some modification in SIP parameters - you need to restart SIP gateway ("killall sipmotor" command).
What about incident on CPU ("incvisu" command - do you have something for SIP).
You use ISDN or ABC-F TG. Dialing via Network|Routing prefixes or ARS?
And may be SIP trace can help you (from doc):
Between the motor and the proxy ("real" SIP messages)

cd /usr2/servers
motortrace n (with two useful trace levels: n = 2 or 3)
traced &

[kimy]

Thanx @ vad.

Will do incvisu when i get back on site. We're using ABC-F TG. Network
What is the correct command for making SIP Trace? Thanks

[vad]

Still the same as written before

And may be SIP trace can help you (from doc):

Between the motor and the proxy ("real" SIP messages)

cd /usr2/servers
motortrace n (with two useful trace levels: n = 2 or 3)
traced &

[kimy]

where can i possibly found this doc so i can study well.Got Links?

[haroun]

to see trunk state
command is trkstat -r N° where N is the sip abcf trunk group number
exemple
(1)pst_cpu20> trkstat -r 1799

Thu Aug 27 10:22:37 CET 2020
+==============================================================================+
| S I P T R U N K S T A T E Trunk group number : 1799 |
| Trunk group name : SipFax |
| Number of Trunks : 4 |
+------------------------------------------------------------------------------+
| Index : 1 2 3 4 |
| State : F F F F |
+------------------------------------------------------------------------------+
| F: Free | B: Busy | Ct: busy Comp trunk | Cl: busy Comp link |
| WB: Busy Without B Channel| Cr: busy Comp trunk for RLIO inter-ACT link |
| WBD: Data Transparency without chan.| WBM: Modem transparency without chan. |
| D: Data Transparency | M: Modem transparency |
+------------------------------------------------------------------------------+
PRESS 'Q' TO QUIT...
that means SIPEXTGW IS UP

[haroun]

AND THIS IS trace sample
1)pst_cpu20> motortrace 3
motortrace (v5.2.0) verbosity = 00000000
sipmotor trace-level set 3 (All traces).
(1)pst_cpu20> traced
** UNIX-trace-daemon started ... (static user group No 1) **

traced started ...
1598520255 -> [ipc_thread] IPC Thread : Ipc reception 1747.
1598520255 -> [ipc_thread] IPC Thread : TCL thread signaled.
1598520255 -> [exec_ipc] in 1746.
1598520255 -> [display_ipc_in] ------------ Begin ---------------
1598520255 -> neqt : 3369 Id : -1
1598520255 -> INVITE
1598520255 -> REQUEST URI : <> 38982000@10.235.96.150:5061 ; user=phone
1598520255 -> FROM : <PosteDeNuit ATTH> 51009@10.235.96.130:5060 ; user=phone
1598520255 -> TO : <> 38982000@10.235.96.150:5061 ; user=phone
1598520255 -> CAC : 0
1598520255 -> neqt CAC : -1
1598520255 -> CLIR : 0
1598520255 -> SDP :
1598520255 -> ADDRESS : 10.235.96.147 :32156
1598520255 -> ALGOS :
1598520255 -> G729
1598520255 -> G723
1598520255 -> PCMA
1598520255 -> 97
1598520255 -> DIRECTION : SEND & RECEIVE
1598520255 -> N_GW_EXT : 1

[poposami]

OXE-AVAYA SIP call disconnect after 31 seconds.pdf

We are facing outgoing calls disconnection from oxe to Avaya after 31 seconds.
Whereas calls from Avaya to OXE R12.2 are okay.Below is call flow where oxe does not acknowledge 200 OK sdp from Avaya
and eventually releases call with bye from Avaya.
I would appreciate suggestions ASAP as customer is very upset.