Difference between revisions of "Asterisk DUNDi debug"

From TD-er's Wiki
Jump to navigationJump to search
(No difference)

Revision as of 15:46, 20 February 2007

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