VicidialNow - System generates wrong CLI in Autodialing

[aamiriqbal]

Hi ALL,

VicidialNow 1.1
Asterisk Version: 1.2.24
VICIDIAL web-client version: 2.0.129

Few days ago the Autodialing was working perfectly fine. All of the sudden it just stopped. I looked into it and upon consulting my VoIP provider they found that the Autodialing is not generating the correct CLI thus calls are being rejected at the Carrier end.

Here is my SIP DEBUG:

--- (0 headers 1 lines) ---
-- AGI Script call_log.agi completed, returning 0
-- Executing DeadAGI("Local/914035902472@default-d4d5,1", "VD_hangup.agi|PRI-----NODEBUG-----16---------------") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/VD_hangup.agi
-- AGI Script VD_hangup.agi completed, returning 0
Scheduling destruction of call '204d17f6007f1c3826c0745c65c3e957@203.99.59.3' in 32000 ms
set_destination: Parsing <sip:66.35.63.247;ftag=as5caea633;lr> for address/port to send to
set_destination: set destination to 66.35.63.247, port 5060
Reliably Transmitting (no NAT) to 66.35.63.247:5060:
BYE sip:66.35.63.247:5061 SIP/2.0
Via: SIP/2.0/UDP 203.99.59.3:5060;branch=z9hG4bK6f6b3417;rport
Route: <sip:66.35.63.247;ftag=as5caea633;lr>
From: "V0922124311000187366" <sip:alcbpo123@203.99.59.3>;tag=as5caea633
To: <sip:14035902472@sip.intlno.com>;tag=f36779220592530f0e183b099133b7b5i
Call-ID: 204d17f6007f1c3826c0745c65c3e957@203.99.59.3
CSeq: 104 BYE
User-Agent: PortaSipFriendly
Max-Forwards: 70
Remote-Party-ID: "V0922124311000187366" <sip:3145581407@203.99.59.3>;privacy=off;screen=no
Authorization: Digest username="alcbpo123", realm="66.35.63.247", algorithm=MD5, uri="sip:66.35.63.247:5061", nonce="d9009e2d6421cef90d1158d443cf757ac448", response="270a9b81d6463b7a476557d635eb8e16", opaque=""
Content-Length: 0

If anybody can be at help please?

Regards,

Aamir

[williamconley]

I am afraid you have posted information that is not particularly helpful. This call has already terminated. And the statement that the system "generates the wrong cli" is similar to saying we're having a lot of weather today. (If the call is not working the way it is expected, obviously something is amiss, and the CLI is the window through which we watch the system, that is all, so what is wrong may or may not be visible through the CLI, depending on your verbosity and debug settings).

So:

Find out what your SIP settings should be from your provider.

Find out from your provider if THEY changed their requirements any time in the near past (and forgot to mention it to you).

Consider upgrading to the most recent version of the software (VicidialNOW.com has a new release, as does ViciBox.com and Vicidial itself, which is the same software in both VicidialNOW and ViciBox).

If you are still having problems, post your CLI output from the moment the call is INITIATED until it gives a reason to end/reject and your dialplan for the dial pattern you are using (ie: if you are dialing 915555551212 post the dial plan for _91NXXNXXXXXX, all three lines).

You can also check your logs in /var/log/asterisk and /var/log/astguiclient.

Good luck.