After some time and serious tweaking my engineer friends and I got a solution - which I will post here for everyone. Hopefully this will help! There are a few things to note to make this work - at least it's how it worked for us...
- Use Notepad++
- Once your done editing the file (the data to change is in all CAPS) save it as an XML file AND MOST IMPORTANT!!!
!!! Save the file without the ".pv" at the end of the name - save it as an .xml - THEN once it's saved and you confirm the
data is correct THEN rename the file with the ".pv" at the end - only change the name NOT the file type... you'll see it on the
file I attached.
Ok, here are the same instructions I left for myself and any of my team. (If the bus hits me and backs up)
1. Verify CNAM is enabled on the provider for the TN
2. 3CX - Trunks or "Voice & Chat" -> IMPORT PROVIDER
3. Upload the "EC Working Trunk Provider.pv" XML file (Give it your own name that's easy to find)
3a -> Setup like normal within 3CX after upload is confirmed...
-name
-default route
-fill in trunk number & Authentication ID
-password
DO NOT SAVE YET....
4. Click DID Numbers - enter DID (no leading 1, unless you need it) - Click the SAVE Icon -looks like a floppy next to the DID
-check to make sure it is correctly listed under DID Number
---DO NOT SAVE YET----
5. OPTIONS
-Caller ID Control
-Verify "From: Display Name" => "CallerDispName" Display name of a caller as it is in From Header - Provided by...
-Verify "Remote Party ID - Calling Party : Display Name" => "OutboundCallerID" Outbound caller Id taken from Extension Settings...
-Verify "P-Asserted Identity : Display Name" = DEFAULT
6. Click Save and call to Verify CALLERNAME delivery is working...(Depending on your provider and if you just enabled CNAM it might take a minute - just start a capture during the tests to make sure CID is being sent in the SIP Header)
This is what worked for us. We have a number of different providers and brands of SIP switches we connect to - all using basic
SIP messaging. If ANYONE needs help with this after being dooped into upgrading to v20 for some customers let me know.
Also, if anyone has any clarification recommendations to help make it easier and more clear for anyone please do so.
This issue has been a huge annoyance and a problem that could have been handled easily from support but wasn't.
Thanks again to everyone who helped!
