Outbound dialing ... stuck situation

[sobek]

Goautodial 2.0 from .iso with manual multi server configuration 1DB&Apache and 2 dialers working fine with outbound predictive dialing | VERSION: 2.2.1-237 BUILD: 100510-2015| Asterisk 1.4.21.2 | No Digium/Sangoma Hardware | No Extra Software After Installation.

I want to route all incoming calls to extension 101. Extension(phone) is created on the same dialer that registration string is set. So it is not a problem of clustering.

I created a defaut DID which is active,
DID route: phone
phone extension 101
server IP xx.xx.xx.xx triple chcecked it is correct
In-Group Call Handle Method: CID

Extension is logged in with x-lite 4

But all hapens when I call DID number from my mobile is

NOTICE[3268]: chan_sip.c:14035 handle_request_invite: Call
from '48616734037' to extension 's' rejected because extension not found.

I'm stuck because what ever i will do with did configuration I still have in CLI same message.

[williamconley]

have you identified which carrier it is resolving to in your debug?

does that carrier have "context=trunkinbound" in the context to send the call to the trunkinbound agi script which will then activate that cool DID you created?

[sobek]

1. Everything is happening on dialer that shows:

NOTICE[3268]: chan_sip.c:14035 handle_request_invite: Call
from '48616734037' to extension 's' rejected because extension not found.

in CLI when I try to call my inbound number.

I have CLI message on same server that I have registration string in carrier settings and extension I want to route to also on the same machine.

2. Yes it has context=trunkinbound in carrier settings.

[williamconley]

have you identified which carrier it is resolving to in your debug?

Just because you have context=trunkinbound in a carrier does not mean that asterisk is matching this inbound call to that carrier.

use your sip debug to verify that it actually is getting to THAT carrier and choosing trunkinbound as a result.

if it is, you'll then need to determine why it is dialing extension "s" instead of the actual DID.

you CAN create an extension s in the trunkinbound and copy the _X. extension already in there to get it into the InGroup agi script, but you will still not have the identity of the DID (which you may be able to locate with SIP debug). it will end up in the "default" DID instead.