vicidial.org

Greetings! This dialer is running:

VERSION: 2.4-306 BUILD: 110109-1205

A strange issue with agent manual dialing. Every other call, the UID for the agent (for example "M11119042900000") is being displayed in the caller ID along with the defined 10-digit oubound CID for the campaign. We're sending ten digits to our carrier, but I suspect this is leading to some call rejections. We have sendrpid=no.

What obvious thing am I missing?

the caller id NAME service is what is kicking in there. what country are you dialing?

what is likely happening is that your carrier is sending your calls out through multiple channels, and one of those channels is actually transmitting (or accepting) the callerid NAME differently than the others (in the US, you never have this problem unless you receive your call through the same carrier, and even then it often doesn't transmit the name).

you could use the loopback dial plan (look up loopback in extensions.conf) temporarily, but be careful it increases the load on your server. you can also discuss with your carrier that they should block the callerid(name) from your system (which may be a function in your web panel if they are complex).

Yeah I know; this is very strange. This is all US48 too.

I will call the carrier this AM. I was simply wondering if there was a facepalm-simple setting so obvious that I completely missed it.

how did you "determine" that every other call was doing this? were you receiving the calls on a specific device? (Perhaps another line on the same carrier ... which would be expected to use the calleridname, since it is THEM transmitting ...?) Try another device to receive the calls that is totally independent.

The same way that I suspect happens with most of us: Some agents report call congestions to their managers. I log in as an agent and start dialing through my test list while grepping the CLI looking for whatever is causing the --CONGESTION--.

And there was my UID showing up on the test phones, my polycom, other's cell phones, etc. Fool around with that, determine that I must be missing something obvious, SVN the latest version of vici, upgrade, try again, and then come crying to the forums. AKA a regular day.

i gathered most of that. but the path to the "test phones" and the "cell phones" is what i'm looking for.

the polycom is likely on a sip carrier and could easily have the callerid name transmitted, not surprising. i've had that a few times.

but the "test phone" phrase doesn't tell me much about the type of phone and carrier. Cell phone is interesting ... i'd like to hear which carrier sent the call and which carrier the cell phone was on that it actually got the CallerID Name from Vicidial (with the M000198581951705 or whatever as the name). that's useful information for troubleshooting AND as general information.

Did you really just put test phone and cell phones in scare quotes?

Outbound is AireSpring. The mobile phones displaying the UID as the caller name are on Verizon and AT&T.

I just opened up a trouble ticket with AireSpring, but in the meantime I'm going to look through the AGI and see if I can't just block the CALLERID(name) there, as this isn't their fault and it's pretty embarrassing to have to block the outbound name at the carrier. Any edits that don't break this dialer I'll post back here.

do NOT modify the callerid(name) (breaks vicidial)

you can only modify the callerid(name) if you use the loopback dialplan (but that adds load, since it actually generates another call). temporary solution, special situation, or lightly loaded servers only.

an interesting concept that the callerid Name field is passing from airespring to AT&T & Verizon. Can you call me with your callerid name set to "Free Cell Phone!!!!" ? I'm on AT&T ...?

I wonder if they "captured" your first outbound call's "Name" and are just using it forever?

Yeah, I'm trying to use the magic of regex to take out the UID of the sip header. But I'm probably going to break it. I guess I can try to Set(CALLERID(name)=) in the dialplan on loopback but that is an ugly hack.

Upon further investigation, this is happening with the other boxes I administer as well. Obviously sending the UID as the cid name is not affecting call completion (my original thought), so the congestions are being caused by something else on this particular box; but Android and iOS phones are displaying the UID. That was news to me. I imagine that I'm going to hear more about this from my clients as the customers they manually dial will ask just who is M0001493999000, but we shall see.

As for the caller id name capture - It is changing dynamically as the UID changes.

Wow. That's a good note for that particular carrier. Inside the US? Never heard that one before. Wonder if Matt has heard this one. Interesting to test the capabilities ...

We have had several clients that have had issues with Airespring. Usually running the calls through the loopback-no-log context or through a gateway that strips out the CIDname will work.