1) Welcome to the Party!
2) As you are obviously new here, I have some suggestions to help us all help you:
When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... 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 "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. 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
3) "... but are just available for any rep ..." is a wee bit vague. Are you using asterisk queues in your vicidial system? How are you making these calls "available" to reps?
If you route this call using standard Vicidial methodology, here is how it would go:
* Call is routed to the Vicidial server either through a "send this call to this IP address" configuration at the carrier, OR a "send this call to this Registered Account" configuration at the carrier. One way or another, the call is then routed to the Vicidial server in question.
* The call arrives and is authenticated to a Carrier (in Admin->Carriers).
* The Carrier configuration setting for "context=xxxx" then determines which Extensions.conf context receives the call.
* Normally, this value should be "trunkinbound", so the call will route to the extnensions.conf context [trunkinbound]
* The entire purpose of the [trunkinbound] context is to route the call to the Vicidial agi/perl scripting system via agi-DID_route.agi
* The agi-DID_route.agi file immediately logs the DID inbound call to vicidial_did_log ... regardless of what happens next, this log entry will survive.
* In addition to being visible directly in mysql (and phpMyAdmin) it is also visible by clicking on "Click here to see a list of recordings and calls for this DID" when modifying the DID in question. Of course, this is "per DID" and requires knowing which DID to check (unlike phpMyAdmin or MySQL which has no such requirement, but obviously requires access outside the Vicidial point-and-click interface).
Happy Hunting!