Hello everyone
I had a question. When I try to make T3 traces, I don't see the caller's number, but I do see another number.
num : a20
num: b103
I'd like to know where these numbers come from because I can't manage to explain the call traces.
explanation on traces
explanation on traces
You do not have the required permissions to view the files attached to this post.
Re: explanation on traces
DID [SDA] NPD
trunk grp management ? ARS
TRY termstat d a20 or tradna
trunk grp management ? ARS
TRY termstat d a20 or tradna
Re: explanation on traces
b103 - VPN overflow prefix (distant)?
Re: explanation on traces
Hello haroun the a20 termstat does not give anything however, it is created as a VPN overflow prefix (type: remote (routing table number)
and Indeed, it is the ARS
You do not have the required permissions to view the files attached to this post.
Last edited by DjeSan on 12 Mar 2024 06:03, edited 1 time in total.
Re: explanation on traces
for VPN overflow - you have somr information in internode links. And in your trace - just small part of information exchange (PBX1 call to PBX2 VPN overflow prefixes (for voice part establishment).
If you need all information - use VPN trace (not simple t3 trace)
Start:
tuner km
tuner clear-traces
tuner +cpu +cpl
actdbg hybr=on
tuner hybrid=on
mtracer -a
Stop:
actdbg all=off
tuner clear-traces
dhs3_init -R MTRACER
If you need all information - use VPN trace (not simple t3 trace)
Start:
tuner km
tuner clear-traces
tuner +cpu +cpl
actdbg hybr=on
tuner hybrid=on
mtracer -a
Stop:
actdbg all=off
tuner clear-traces
dhs3_init -R MTRACER