Page 1 of 1
explanation on traces
Posted: 08 Mar 2024 05:06
by DjeSan
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.
Re: explanation on traces
Posted: 09 Mar 2024 15:28
by haroun
DID [SDA] NPD
trunk grp management ? ARS
TRY termstat d a20 or tradna
Re: explanation on traces
Posted: 10 Mar 2024 23:16
by vad
b103 - VPN overflow prefix (distant)?
Re: explanation on traces
Posted: 12 Mar 2024 06:01
by DjeSan
haroun wrote: ↑09 Mar 2024 15:28
DID [SDA] NPD
trunk grp management ? ARS
TRY termstat d a20 or tradna
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
Re: explanation on traces
Posted: 12 Mar 2024 06:02
by DjeSan
vad wrote: ↑10 Mar 2024 23:16
b103 - VPN overflow prefix (distant)?
Indeed, that's it, why then, I can't see the caller's number please
Re: explanation on traces
Posted: 12 Mar 2024 23:27
by vad
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