Inbound call problem - can someone help?


Could someone possibly take a quick look at my extensions.conf below please.

I am having an issue. As you can see I have 5 DDI’s configured, 2 of them are configured to forward to IVR and 3 are configured to forward direct to extensions. The IVR setup (TEST-IVR) is configured with 3 options with forwarding to 3 extensions.

The problem is, whenever someone rings any of the 5 DDI’s, they still hear the IVR audio message (even on the numbers which are not configured to go there). Also when the IVR audio file is playing, extension 102 and 103 rings, before the caller has even pressed any options. Can you see an issue with the below configuration?

Any help would be great, thank you.


exten => 101,1,Answer()
exten => 101,n,Dial(SIP/101,20,tr)
exten => 101,n,Hangup

exten => 102,1,Answer()
exten => 102,n,Dial(SIP/102,20,tr)
exten => 102,n,Hangup

exten => 103,1,Answer()
exten => 103,n,Dial(SIP/103,20,tr)
exten => 103,n,Hangup


exten => 02031234567,1,Goto(TEST-IVR,s,1)

exten => 02031234568,1,Goto(TEST-IVR,s,1)

exten => 02031234569,1,Dial(SIP/102)

exten => 2548981,1,Dial(SIP/103)

exten => 02031234570,1,Dial(SIP/103)

exten => _X.,1,Dial(SIP/sip-out/${EXTEN})

exten => s,1,Background(test-ivr)
exten => 1,1,Dial(SIP/101)
exten => 2,1,Dial(SIP/102)
exten => 3,1,Dial(SIP/103)

Please, provide log of the call.

Fixed the problem. All of the DDI’s were coming in on the same SIP registration, it looks like my SIP trunk provider was passing every number linked to the trunk account along with the incoming call rather than just the number dialled, causing all of the extension rules to start. At least that’s how it looked from the call log. Is that normal?

I configured the DDI’s to forward direct to sip:ddi@myserver instead of through the SIP registration, it now works perfectly.

I am completely new to Asterisk, only installed it this morning for the first time - the above diagnosis could well be wrong.

But main thing, it now works.

Thank you for offering assistance Samael28.

More likely it was matching on IP address, rather than user.