Inbound Calling problem

Any and all non-support discussions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Inbound Calling problem

Postby raju » Thu Jul 26, 2012 5:06 am

Hi,

i am trying to call my DID number, but its not landing on agent CLI. and i am getting the error: but no route to the "t" of context ='trunkinboung'


please help me.
and please share the Australia dial plan for incoming


thanks & regards
raju
raju
 
Posts: 48
Joined: Fri Jun 29, 2012 10:08 pm

Re: Inbound Calling problem

Postby striker » Thu Jul 26, 2012 11:18 pm

post you sip setting used and also screeshot of the asterisk cli when you make incomming call ( one single call )
www.striker24x7.com www.youtube.com/c/striker24x7 Telegram/skype id : striker24x7
striker
 
Posts: 962
Joined: Sun Jun 06, 2010 10:25 am

Inbound Calling problem

Postby raju » Fri Jul 27, 2012 1:02 am

[siptrunk]
disallow=all
allow=ulaw
type=friend
username=xxxxxxx
secret=xxxxxx
host=ip
dtmfmode=rfc2833
context=trunkinbound
qualify=1000

Global String:SIPTRUNK = SIP/siptrunk

exten => _61XXXXXXXXXX.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _61XXXXXXXXXX.,2,Dial(${SIPTRUNK}/${EXTEN},,tToR)
exten => _61XXXXXXXXXX.,3,Hangup
raju
 
Posts: 48
Joined: Fri Jun 29, 2012 10:08 pm

Re: Inbound Calling problem

Postby williamconley » Thu Aug 09, 2012 2:42 pm

add an extension "t" to "[trunkinbound]" in extensions.conf. Copy extension "_X." to create it. If this works, you'll have some more work to find out how they are sending the identity of the DID, cuz "t" isn't a valid one. LOL (but that will get this one working ... you'll just never be able to distinguish between this one and the next one because it, too, will be "t", so you'll have to work that out!)

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20258
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 96 guests