CallerID works on calls to cell not landline

[llc1209]

Have caller id set up in campaign. But oddly when testing receiving landline phone gets 'private name' or 'private caller' as caller id, no number. Receiving cell phone will see the number displayed on caller id. Softphone x-lite. Have not found anyone else with this problem. Thanks.

Vici version 2.6.B0.5
Asterisk 1.4.44 VICI
Linux

[williamconley]

you will need to show how your call is dialed. outbound carrier dialplan.

also: are these "vicidial autodialed calls" or manual dialed calls by logged in agents or are they dialed directly in the soft phone but passing through the vicidial server on the way to the carrier or just soft phone straight to the carrier.

also: How did you install your system? (name of the .iso and version number ...)

[llc1209]

Sorry, will have to look up the .iso name and version. I downloaded and burned the CD, but someone else ran the installation. Now, I'm trying to administer it.

Here's the dialplan (not sure why it has test in it, or if this was the default dialplan:
exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(${TESTSIPTRUNK}/${EXTEN:2},,To)
exten => _91NXXNXXXXXX,3,Hangup

[williamconley]

also: are these "vicidial autodialed calls" or manual dialed calls by logged in agents or are they dialed directly in the soft phone but passing through the vicidial server on the way to the carrier or just soft phone straight to the carrier.

[llc1209]

Oops.
They are manual dialed calls by logged in agents, but have also tried dialing directly in the soft phone. I believe passing through the vicidial server on the way to the carrier. Thanks.

[williamconley]

Cool. Progress!

Good to note that it is possible for manual dialed calls to take a different path than autodialed (in your campaign setup, manual dial prefix can cause this ...), and definitely easy for "direct dialing" calls to take yet another path.

If you call without "vicidial" being involved, your callerid will NOT be set by Vicidial and you should use a dialplan that will set your callerid for you. Creating a new dialplan specifically for that purpose (1NXXNXXXXXX on all three lines ... without the 9 ... and with EXTEN:1 or EXTEN instead of EXTEN:2) ... then your agents don't need to dial "9" before the phone number.

You should also try with EXTEN:1 in the dialplan you posted already to see if providing the "1" through to the carrier during outbound dialing has any effect (it shouldn't ... but this is open source programming, linux, and telephony ... so anything is possible and worth a try! LOL). FYI: the :2 removes the first two digits of the extension (variable ${EXTEN} is all the digits ... ${EXTEN:2} is with the first two digits removed, the 91)

Provide an asterisk CLI example of a "good" (callerid showed properly) vs a "bad" (no callerid). See if there is a noticeable difference (other than the number dialed, of course ... XXXX for the last four digits of the phone number dialed and .xxx the last digit(s) of the IP address to avoid posting any "personal" information if you fear for data privacy).

NOT 3000 lines of unrelated code. Test calls in a controlled situation (no other calls) and only from the inception of the call to the moment of "ring" (when you see the bad callerid ...). Anything beyond that is irrelevant and may stop a technician from bothering to read your actual necessary code, so leave it off for the best results.

[llc1209]

Thanks. Will let you know how it goes as soon as I get a chance to test.