Asterisk DUNDi debug

From TD-er's Wiki
Jump to navigationJump to search

When making a call from extension 1301 to 1001, the lookup has to pass 2 PBX's.

Situation

Extensions:

  • 1301 is connected to PBX1
  • 1601 is connected to PBX2
  • 1001 is connected to PBX3

Peering:

  • PBX1 (192.168.1.101) peers with PBX2 (192.168.1.103) and vice-verse.
  • PBX2 (192.168.1.103) peers with PBX3 (192.168.1.106) and vice-verse.
  • PBX1 does not peer with PBX3 and vice-verse.

In the CLI this shows as follows:

PBX1:

asterisk1*CLI> dundi show peers
EID                  Host                Model      AvgTime  Status
00:0c:29:a7:e0:73    192.168.1.103   (S) Symmetric  Unavail  OK (2 ms)
1 dundi peers [1 online, 0 offline, 0 unmonitored]

PBX2:

asterisk1*CLI> dundi show peers
EID                  Host                Model      AvgTime  Status
00:0c:29:97:0b:98    192.168.1.101   (S) Symmetric  Unavail  OK (3 ms)
00:0c:29:d2:d8:ec    192.168.1.106   (S) Symmetric  Unavail  OK (1 ms)
2 dundi peers [2 online, 0 offline, 0 unmonitored]

PBX3:

asterisk1*CLI> dundi show peers
EID                  Host                Model      AvgTime  Status
00:0c:29:a7:e0:73    192.168.1.103   (S) Symmetric  Unavail  OK (1 ms)
1 dundi peers [1 online, 0 offline, 0 unmonitored]


For ext. 1301 to call 1001, all 3 PBX's schould participate in the lookup.

DUNDi Debug-info

In Asterisk's CLI, you can get debug-info with the command dundi debug. To switch the debug off, enter dundi no debug

Each peer will stay in contact with its peers by sending some sort of ping-packets to eachother at regular intervals. Therefore always switch the debug-mode off before analysing the output.

PBX 1

asterisk1*CLI> dundi debug
DUNDi Debugging Enabled
    ETx-Frame Retry[No] -- OSeqno: 000 ISeqno: 000 Type: DPDISCOVER   (Command)
          Flags: 00 STrans: 14133  DTrans: 00000 [192.168.1.103:4520]
        VERSION         : 1
        DIRECT EID      : 00:0c:29:97:0b:98
        CALLED NUMBER   : 1001
        CALLED CONTEXT  : priv
        TTL             : 32
Tx-Frame Retry[No] -- OSeqno: 000 ISeqno: 000 Type: ENCRYPT      (Command)
     Flags: 00 STrans: 14133  DTrans: 00000 [192.168.1.103:4520]
   ENTITY IDENT    : 00:0c:29:97:0b:98
   SHAREDKEY       : [ 79 71 ..... f9 00 bc ]
   SIGNATURE       : [ a1 b3 ..... 7a 5c 14 ]
  ENCDATA         : [IV 302f4771ce6cae684c01631987a2e264] 4 encrypted blocks
Rx-Frame Retry[No] -- OSeqno: 000 ISeqno: 001 Type: ACK          (Response)
     Flags: 00 STrans: 18399  DTrans: 14133 [192.168.1.103:4520]
Rx-Frame Retry[No] -- OSeqno: 000 ISeqno: 001 Type: ENCRYPT      (Command)
     Flags: 00 STrans: 18399  DTrans: 14133 [192.168.1.103:4520]
   ENCDATA         : [IV 7212e969e4452c685dcecc777b15ea12] 6 encrypted blocks
   Erx-Frame Retry[No] -- OSeqno: 000 ISeqno: 001 Type: DPRESPONSE   (Response)
         Flags: 00 STrans: 18399  DTrans: 14133 [192.168.1.103:4520] (Final)
       ANSWER          : [EXISTS|NOUNSLCTD|NOCOMUNSLTD] 0 <IAX/priv:LA.....Ucw@192.168.1.106/1001> from [00:0c:29:d2:d8:ec]
       HINT            : [UNAFFECTED]
       EXPIRATION      : 5


PBX 2