Inbound numbers not identified [resolved]

[AlSam]

I am having trouble identifying inbound numbers. It seems when the agent receives a call he/she can see the caller's number on screen, yet when I check the name of the resulting recording, the phone number is not there. In its place is the word Anonymous. However this only happens under certain circumstances. Agents can receive calls two ways: 1. Clients call an 800 number. These calls are routed directly from the telephony provider to the Vicidial equipment. 2. Clients call a local number which goes to an old Nortel PBX and then transferred (trunk to trunk) to the Vicidial equipment. Only the calls that come in directly to the Vicidial show up as Anonymous in the call recording's name. Any help would be appreciated in this matter.

[callcrazy]

Perhaps the provider of the 800 service going directly to vici isn't offering cnam lookups as part of the service package purchased or it's not enabled by default.

[williamconley]

Welcome to the party AlSam!

when you post, please post your entire configuration including (but not limited to) your installation method and OS with kernel or version, vicidial version and build, 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.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

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)

____

Also, are you referring to callerid NAME or callerid NUMBER or both?

when I check the name of the resulting recording, the phone number is not there

Where are you checking this? (URL without your FQDN would help, or a screen shot ...)

[AlSam]

Thanks for your help. Through some further testing I found out that the customer has more than one provider for their PBX lines and one of the two does not provide the number ID for the originator of the call.

[williamconley]

Thanks for your help. Through some further testing I found out that the customer has more than one provider for their PBX lines and one of the two does not provide the number ID for the originator of the call.

excellent! thanks for posting back your solution!

[AlSam]

williamconley, How can I go about finding out the information requested earlier, specifically "...and OS with kernel or version, vicidial version and build, asterisk version". Thanks.

[williamconley]

Valid question!

I don't think there's a sticky specifying exactly how you can get all this, but I post it all the time for specific pieces of this puzzle, so here it is all at once:

Vicibox X.X from .iso |

This would be in the file name of the .iso image you downloaded (whether ViciBox, VicidialNOW or any OS's install .iso)

If you use something OTHER than ViciBox or VicidialNOW, it is recommended to list the OS name (site you downloaded it from is usually it) and the kernel which installed.

If you installed with ViciBox 3.0 or after, it will appear each time you log in via ssh.

To get your Kernel:

Code: Select all

uname -r

Often to get your OS name (not foolproof):

Code: Select all

cat /etc/*version
cat /etc/*release

Vicidial X.X.X Build XXXX |

Bottom right corner of virtually every admin page in VICIdial

Asterisk X.X.X |

Code: Select all

asterisk -R

The next three items you SHOULD know as the administrator of your system(s), but I leave room for the freshly arrived administrator who just "stepped into the fray", as it were:

Single Server |

Admin->Servers (how many?)

No Digium/Sangoma Hardware |

Code: Select all

lsmod | grep dummy

If the dummy module is in use, you likely have no hardware.

If you DO have hardware, it is recommended to list the actual model number, not just the "module it loads" and the manufacturer (watching out for "knockoffs" that imply they are digium in some fashion)

No Extra Software After Installation |

OK, here I can't help as much, but as a rule if you look in your web root (/var/www/ or /srv/www/htdocs/) you may find hints of what ELSE may be installed. Many .isos for VICIdial also install vtigercrm and/or phpMyAdmin. agc, astguiclient, and vicidial folders are expected as parts of VICIdial itself.
____________

I think it would be a good thing if anyone were to completely reproduce this with any additions that may "complete" it and eventually make it a sticky (although there may be one already which I overlooked).

[AlSam]

Thanks again.