INBOUND DID call not Palced IN IN-GROUP-

[heart200306]

Dear Team
inbound call is not place in queue would you please help me .


Kernel:
Linux ccdial1 3.1.10-1.19-default #1 SMP Mon Feb 25 10:32:50 UTC 2013 (f0b13a3) x86_64 x86_64 x86_64 GNU/Linux
VERSION: 2.6-396a
BUILD: 130402-2322

Server :Blended

Agent Login successful and Ext ringing test call …..

[Apr 17 07:47:22] > Channel SIP/201-00000068 was answered.
[Apr 17 07:47:22] -- Executing [8600051@default:1] MeetMe("SIP/201-00000068", "8600051|F") in new stack
[Apr 17 07:47:22] == Parsing '/etc/asterisk/meetme.conf': [Apr 17 07:47:22] Found
[Apr 17 07:47:22] == Parsing '/etc/asterisk/meetme-vicidial.conf': [Apr 17 07:47:22] Found
[Apr 17 07:47:22] -- Created MeetMe conference 1023 for conference '8600051'
[Apr 17 07:47:22] -- <SIP/201-00000068> Playing 'conf-onlyperson' (language 'en')
[Apr 17 07:47:24] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 17 07:47:28] Really destroying SIP dialog 'ZmNhZDAwYTAyODkxMWRlMTE4ZTEyNDgxMDZmNzgyODQ.' Method: REGISTER
[Apr 17 07:47:29] Really destroying SIP dialog 'Y2NkODkwZmI3YzY0MDhjNzZiNDk0NTE1OTljZTUxNjQ.' Method: REGISTER
[Apr 17 07:47:32]
<--- SIP read from X.X.X.X :45508 --->

When I called to DID for inbound not finding call in agent login panel

[Apr 17 09:44:51] NOTICE[2129]: chan_sip.c:17850 sip_poke_noanswer: Peer '201' is now UNREACHABLE! Last qualify: 439
[Apr 17 09:45:02] NOTICE[2129]: chan_sip.c:14057 handle_response_peerpoke: Peer '201' is now Reachable. (439ms / 2000ms)
[Apr 17 09:45:04] NOTICE[2129]: chan_sip.c:15804 handle_request_invite: Call from '201' to extension '02035709952' rejected because extension not found.
[Apr 17 09:45:08] == Parsing '/etc/asterisk/manager.conf': [Apr 17 09:45:08] Found
[Apr 17 09:45:08] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 17 09:45:08] == Parsing '/etc/asterisk/manager.conf': [Apr 17 09:45:08] Found
[Apr 17 09:45:08] == Manager 'sendcron' logged on from 127.0.0.1
[Apr 17 09:45:08] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 17 09:45:09] == Manager 'sendcron' logged off from 127.0.0.1
[Apr 17 09:45:10] == Refreshing DNS lookups.
[Apr 17 09:45:22] NOTICE[2129]: chan_sip.c:15804 handle_request_invite: Call from '201' to extension '02035709952' rejected because extension not found.

[williamconley]

1) Thanks for posting your vicidial version with build, but here are some other newbie suggestions that may be useful for you (and for us to help you ...):

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

2) you are trying to dial a DID from a user's phone. this does not work as you are trying to reach an inbound line while dialing outbound.

3) please use the Vicidial Manager's Manual for basic setup questions. That's what it is there for, I believe it has a section for Inbound DID setup. Makes life simpler.

4) Inbound call configuration is handled in multiple stages: first you must cause the call to arrive at your server; second you must cause the call to be handled by Vicidial within the server; third you use Vicidial to route the call to wherever you want. You are at stage one: cause the all to arrive at your server. This is handled at the Carrier's site in conjunction with your Admin->Carrier settings (which may require a "register string" to notify the carrier of your IP to acquire the call).

5) If you hit a snag in the Manual, bring us the Manual version, Page, Line and a detailed description of the "Problem" you are experiencing and we'll walk you through it.

6) Happy Hunting!

[heart200306]

Thank you for quick reply . Let me reconfigure campagion and others using follow Manager Manual 2012-04-29 version . If any trouble I will come back to you .Thanks

[heart200306]

Thank you to All Inbound Problem is solved . I was wrong cause when I logged in a agent ..System auto ringing in my ext but I had disconnect call as a reason inbound call are failed due to ext not finding ...