Page 1 of 1

P'Asserted Identity Showing Vicidial UID

PostPosted: Fri May 27, 2022 9:32 am
by syedfahim786
Hello All,

We ran into some issues with the Caller ID name for the Canadian Project. We set the P' Asserted Identity with our company name and number. But it is showing two P'Asserted Identities. The first is the one that we set and the second is the one that Vicidial UID is auto-generated. Check the photo attached. How can we fix this? Any suggestions!!

Check the photo here:
Image


Installation Details: Vicidial 9 | Scratch installed on Centos7 | Asterisk 13.29.2-vici | SVN Version:3608 | Version: 2.14b0.5 | DB Schema Version: 1661

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Sat May 28, 2022 12:50 pm
by carpenox
Try a loopback dialplan such as this:

exten => _81NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _81NXXNXXXXXX,n,NoOp(MY CALLERD !!!! ${CALLERID(all)})
exten => _81NXXNXXXXXX,n,Set(_CALLERID(num)=${CALLERID(num)})
exten => _81NXXNXXXXXX,n,Dial(IAX2/ASTloop/9${EXTEN:1},,tTo)
exten => _81NXXNXXXXXX,n,Hangup()

exten => _91NXXNXXXXXX,1,Set(CALLERID(num)=${CALLERID(num)})
exten => _91NXXNXXXXXX,n,Set(CALLERID(name)=${CALLERID(num)})
exten => _91NXXNXXXXXX,n,NoOp(MY CALLERD !!!! ${CALLERID(all)} ${CALLERID(num)} ${CALLERID(name)})
exten => _91NXXNXXXXXX,n,Dial(SIP/${EXTEN:1}@TILTX,,tTo)
exten => _91NXXNXXXXXX,n,Hangup()


Hope this helps

Chris

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Sun May 29, 2022 3:38 am
by syedfahim786
Hello Chris,

Thanks for writing. We tried to follow one of the old posts regarding the same matter to use the loopback in the extensions.conf file.

http://vicidial.org/VICIDIALforum/viewt ... =4&t=38023


We were able to take off the vicidial UID which was passing to the carriers. But it started another issue, the CID name is showing something like:
From: "\"CIDNAME\"" <sip:1xxxxxxxxxx@xxx.xxx.xxx.xxx:5060>;tag=as238c38df

Why we have extra forward slash?

Check the photo:
https://ibb.co/JjDFn5G

Image

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Sun May 29, 2022 12:22 pm
by williamconley
In the older systems you were expected to change the string 'CIDNAME' to your company name. If you just used it as it was in the extensions.conf file, you just need to change that string to your name. But if you put any extra characters in ... such as quotation marks ...

Perhaps you should post your extensions.conf here so we can see what you did? Just change the name to XYZCorp if you don't want to share your company name.

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Sun May 29, 2022 5:17 pm
by syedfahim786
Hello William,

Thanks for writing!! Here are the extensions.conf file:

We uncommented the following lines in extensions.conf:

exten => _91NXXNXXXXXX,1,Set(CALLERID(name)="XYZCorp")
exten => _91NXXNXXXXXX,n,AGI(agi-CANADA_PRI_CIDname.agi)
exten => _91NXXNXXXXXX,n,Dial(SIP/1234*${EXTEN:1}@Flowroute,,tTo)
exten => _91NXXNXXXXXX,n,Hangup()

And

exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,n,Dial(${TRUNKloop}/888${EXTEN:2},55,o)
exten => _91NXXNXXXXXX,n,Hangup()
exten => _888NXXNXXXXXX,1,Goto(loopback-no-log,91${EXTEN:3},1)
exten => _888NXXNXXXXXX,n,Hangup()

exten => 8889990011112,1,Goto(loopback-no-log,9990011112,1)
exten => 8889990011112,n,Hangup()


While the Dialplan Entry is:
exten => _91XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX,n,SipAddHeader(P-Asserted-Identity: "XYZCorp" <sip:${CALLERID(num)}@ap-southeast-sin.sip.flowroute.com>)
exten => _91XXXXXXXXXX,n,Dial(SIP/1234*${EXTEN:1}@Flowroute,,tTo)
exten => _91XXXXXXXXXX,n,Hangup()

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Mon May 30, 2022 2:26 pm
by williamconley
Why we have extra forward slash?


exten => _91XXXXXXXXXX,n,SipAddHeader(P-Asserted-Identity: "XYZCorp" <sip:${CALLERID(num)}@ap-southeast-sin.sip.flowroute.com>)


exten => _91NXXNXXXXXX,1,Set(CALLERID(name)=XYZCorp)


change that string to your name. But if you put any extra characters in ... such as quotation marks ...


Have you tried
Code: Select all
exten => _91NXXNXXXXXX,1,Set(CALLERID(name)=XYZCorp)

and/or
Code: Select all
P-Asserted-Identity: XYZCorp <sip:${CALLERID(num)}@ap-southeast-sin.sip.flowroute.com>


instead of
Code: Select all
exten => _91NXXNXXXXXX,1,Set(CALLERID(name)="XYZCorp")

and/or
Code: Select all
P-Asserted-Identity: "XYZCorp" <sip:${CALLERID(num)}@ap-southeast-sin.sip.flowroute.com>

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Tue May 31, 2022 5:13 pm
by syedfahim786
Thanks, William. That's showing the correct name now!!

But my carrier is saying they are not getting any P'Asserted Identity. They said: "we're seeing "XYZCorp" being sent over in the From field and no P-Asserted-Identity being sent over. You'll need to set the P-Asserted-Identity in the PBX.

In the sip.conf file we have
trustrpid=no
sendrpid=pai

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Tue May 31, 2022 8:42 pm
by williamconley
When using the Vicidial Loopback methods, there are two calls.

The first call "loops back" to the same server via an IAX2 dial, which is then routed to the "loopback" context. Then a 2nd call is generated. Is your p'asserted identity on that first call, or the second one?

Since the first call is ... in-house, it would be pointless to have p'asserted on that. So only the second call requires this is if you need it for your carrier.

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Wed Jun 01, 2022 12:48 am
by syedfahim786
We have set the P'Asserted Identity only on the dialplan as mentioned above.


syedfahim786 wrote:While the Dialplan Entry is:
exten => _91XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX,n,SipAddHeader(P-Asserted-Identity: XYZCorp <sip:${CALLERID(num)}@ap-southeast-sin.sip.flowroute.com>)
exten => _91XXXXXXXXXX,n,Dial(SIP/1234*${EXTEN:1}@Flowroute,,tTo)
exten => _91XXXXXXXXXX,n,Hangup()

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Wed Jun 01, 2022 3:14 pm
by williamconley
Grab a SIP debug from that outgoing call, which should show the p'assert. Send it to the carrier and ask if there's a reason it would disappear between your server and theirs.

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Sat Jun 04, 2022 11:45 am
by syedfahim786
williamconley wrote:Grab a SIP debug from that outgoing call, which should show the p'assert. Send it to the carrier and ask if there's a reason it would disappear between your server and theirs.



SIP debug is only showing From and To. But no P'Asserted Identity.

Image

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Sun Jun 05, 2022 12:08 pm
by williamconley
1) Your dialplan shows the assert header being added

2) Your SI P debug fails to show the header

Now you have to confirm:
* that the dialplan you showed is actually the one in use. Best method would be to remove all other traffic from the system and make a test call. you'll see the dialplan execute just before the sip packet debug is generated. that should confirm/deny whether the extension adding the assert header actually executes
* that the dialplan you showed is properly formatted (if the previous step shows the dialplan line executing with the assert, but the SIP debug still has no assert). In that case, you'll need a generic test-case scenario to prove the method of adding the assert line into a sip invite.

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Sat Jun 25, 2022 1:57 pm
by syedfahim786
Thanks, William for all your valuable suggestions.

I am a little curious to know what will happen if we can change extensions.conf file like:

exten => _91NXXNXXXXXX,1,Set(CALLERID(name)=XYZ Corp)
exten => _91NXXNXXXXXX,n,SipAddHeader(P-Asserted-Identity: "XYZ Corp" <sip:${CALLERID(num)}@13.xxx.xxx.xx>)
;exten => _91NXXNXXXXXX,n,AGI(agi-CANADA_PRI_CIDname.agi)
exten => _91NXXNXXXXXX,n,Dial(SIP/111111*${EXTEN:1}@Flowroute,,tTo)
exten => _91NXXNXXXXXX,n,Hangup()

Using the above extension (disabled Canada.agi) increased call connectivity and callbacks. Both with and without Canada.agi CIDname was successfully displayed.

Cheers

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Sat Jun 25, 2022 2:51 pm
by williamconley
You should read the notes at the top of the agi script in question. There are usually pretty good notes in all the files in Vicidial. Of course, the agi script isn't in English but perl agi scripting also isn't rocket science and is Pretty Close to English. 8-)

Re: P'Asserted Identity Showing Vicidial UID

PostPosted: Sun Oct 16, 2022 9:28 am
by jamiemurray
I use this for setting Caller ID name for calls to Canada without lookback calls (which increase load) and it works beautifully.

If you're not using caller ID name (the value is blank), then the caller id number will be used as the "name" in the caller id, overriding the vicidial call id without amending the From header and breaking auto-dialling.

Note: Not all carriers support using P-Asserted-ID as the caller ID override and some require different formats. Test it first or check with the carrier.

In your carrier dialplan entry:

Code: Select all
exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
same => n,GotoIf($["${CUT(SIPADDHEADER01, ,2-)}" = ""]?basicpaid)
same => n,SIPAddHeader(P-Asserted-Identity: "${CUT(SIPADDHEADER01, ,2-)}" <tel:${CALLERID(num)}>)
same => n,Goto(dial)
same => n(basicpaid),SIPAddHeader(P-Asserted-Identity: "${CALLERID(num)}" <tel:${CALLERID(num)}>)
same => n(dial),Dial(${CARRIER}/${EXTEN:1},${CAMPDTO},To)
same => n,Hangup()


For easy Canada Caller ID name support:

In system settings:
OpenSIPs CID Name Support = 1

In Campaign Detail View:
Campaign CID Name = [Your CID Name as you want it displayed]