Problem with DUNDi


#1

hi all,
can someone help me solve this problem about DUNDi. I work by following the ebook asterisk 1.8 -the definitive guide.
I try to configure two asterisk VMs which connect together by using Dundi.
PC : IP: 192.168.0.103 MAC: 00:0C:29:57:89:B3 and the dundi.conf is:

[general]
department=PC
organization=PC organization.
locality=Goden
stateprov=ST
country=Vn
email=xxx@gmail.com
phone=0xxx
bindaddr=0.0.0.0
port=4520
entityid=00:0C:29:57:89:B3
ttl=32
autokill=yes

[mappings]
extensions => point,0,SIP,dundi:123456@192.168.0.103/${NUMBER},nopartial
[00:0C:29:06:59:EE]
model   =       symmetric
;auth   =       rsa
host    =       192.168.0.100
inkey   =       Laptop
outkey  =       PC
qualify =       yes
dynamic =       yes
permit  =       extensions
include =       extensions
order   =       primary

Laptop : IP: 192.168.0.100 MAC: 00:0C:29:06:59:EE
The dundi.conf configuration in Laptop is the same with PC.(change IP, entityid,…)
in the system, i can dundi lookup, and everything work well.
In PC sip.conf and extensions.conf, i add:

In PC with ip address 192.168.0.103:
sip.conf:
[dundi]
type=friend
secret=123456
context=DUNDi_Incoming
disallow=all
allow=ulaw
allow=alaw
extensions.conf: 
[DUNDi_Incoming]
exten => 890,1,Verbose(2,Test dundi remote connection)
exten => 890,2,Dial(SIP/dundi:123456@192.168.0.100/${EXTEN},30)
exten => 890,n,Hangup()

In Laptop with ip address 192.168.0.100:

extensions.conf: 
[LocalSets]
exten => 890,1,Verbose(2,Test dundi remote connection)
exten => 890,2,Dial(SIP/dundi:123456@192.168.0.103/${EXTEN},30)
exten => 890,n,Hangup()

i register SIP 890 in PC(192.168.0.103) and SIP 789 with context “LocalSets” in Laptop(192.168.0.100)
This is the result in asterisk command line:
SIP 789 call 890:

== Using SIP RTP CoS mark 5
    -- Executing [890@LocalSets:1] Verbose("SIP/789-00000003", "2,Test extension to place call to remote server") in new stack
  == Test extension to place call to remote server
    -- Executing [890@LocalSets:2] Dial("SIP/789-00000003", "SIP/dundi:123456@192.168.0.103/890,30") in new stack
[Mar 24 03:41:02] NOTICE[3616]: chan_sip.c:25720 sip_request_call: Conflicting extension values given. Using 'dundi' and not '890'
  == Using SIP RTP CoS mark 5
    -- Called SIP/dundi:123456@192.168.0.103/890
[Mar 24 03:41:03] NOTICE[3561]: chan_sip.c:19556 handle_response_invite: Failed to authenticate on INVITE to '"Test" <sip:789@192.168.0.100>;tag=as2008e0a1'
    -- SIP/192.168.0.103-00000004 is circuit-busy
  == Everyone is busy/congested at this time (1:0/1/0)
    -- Executing [890@LocalSets:3] Hangup("SIP/789-00000003", "") in new stack
  == Spawn extension (LocalSets, 890, 3) exited non-zero on 'SIP/789-00000003'

however, i use asterisk console in Laptop 192.168.0.100, i can dial to remote host like that:
In 192.168.0.100:

console dial 890@LocalSets
  == Console is full duplex
[Mar 24 03:42:24] NOTICE[3560]: console_video.c:133 console_video_start: voice only, console video support not present
    -- Executing [890@LocalSets:1] Verbose("Console/dsp", "2,Test extension to place call to remote server") in new stack
  == Test extension to place call to remote server
    -- Executing [890@LocalSets:2] Dial("Console/dsp", "SIP/dundi:123456@192.168.0.103/890,30") in new stack
[Mar 24 03:42:24] NOTICE[3618]: chan_sip.c:25720 sip_request_call: Conflicting extension values given. Using 'dundi' and not '890'
  == Using SIP RTP CoS mark 5
    -- Called SIP/dundi:123456@192.168.0.103/890
    -- SIP/192.168.0.103-00000005 is ringing
    -- SIP/192.168.0.103-00000005 answered Console/dsp
 << Console call has been answered >>

In 192.168.0.103:

Using SIP RTP CoS mark 5 -- Executing [dundi@default:1] Verbose("SIP/192.168.0.100-00000000", "2,Connection") in new stack == Connection -- Executing [dundi@default:2] Dial("SIP/192.168.0.100-00000000", "SIP/890") in new stack == Using SIP RTP CoS mark 5 -- Called SIP/890 -- SIP/890-00000001 is ringing -- SIP/890-00000001 answered SIP/192.168.0.100-00000000 -- Locally bridging SIP/192.168.0.100-00000000 and SIP/890-00000001

In ebook, it tells me when a call happens, the incoming call will go follow the SIP dundi that we defined in SIP.conf and go to context DUNDi_Incoming. However, i see it’s not true, the SIP dundi is not concerned in this case. and the incoming call comes to the “default” context insted of “DUNDi_Incoming” context.
Please help me to solve this problem? i changed the configuration follow the pdf: Dundi so easy. However, the problem happens the same.
Sorry about my english if it’s not easy to understand:)


#2

Please someone helps me!! i try with it more than three days. i can not find any way to fix this problem. Up up :smiley:


#3

Please help me solve this problem. I can not fix it by myself T.T