Thanks David, that’s really useful.
The word ‘Token’ lead me to finding ‘Token Help’ as a drop down on the dial plan pages. That in turn lead me to finding examples of settings that work to pass the caller ID to the SIP destination. For others reading in the future,
Source - enter "IF:02..,TELC:<.*>" #where 02.. is the source, like 0201
Destination - enter "IF:9901,TELC:<1>"
The observation here is that <.*> in the source collects the caller ID and <1> drops it on the destination.
Checking the vega log (by telnet, it didn’t like SSH, but the log was the same as I found through the web interface);
LOG: 12/07/2016 15:53:34.152 POTS (I)R01Cac incoming
call ref=[f10600d3] srce=TEL:07912933052 [0]
LOG: 12/07/2016 15:53:34.170 ROUTER (I)R0bC00 FINDROUTE profile:20(To_SIP) plan:1
call ref=[f10600d3] <-- POTS [1,1] dest=
--> SIP [2,1] dest=TEL:0201,TELC:077XXXXXX #number hidden for this forum post
LOG: 12/07/2016 15:53:34.170 ROUTER (I)R0bC00 call proceeding
call ref=[f10600d3]
LOG: 12/07/2016 15:53:39.435 SIP (I)R03C1c connect g711Alaw64k (Profile 1 - Voice)
call ref=[f10600d3]
LOG: 12/07/2016 15:56:00.522 SIP (I)R04C1c disconnect(disc ind) 16
call ref=[f10600d3]
LOG: 12/07/2016 15:56:00.532 POTS (I)R05Cac disconnect call cause 16
call ref=[f10600d3]
So, I now see the Vega is passing the Caller ID. Only problem is, FreePBX still shows ‘vega’ as the ID. I’ve spent a few more hours googling and reading and I know I’ll get there eventually, but if you can point me where to look I’d be grateful.
The best hint I’ve found in the FreePBX logs so far is;
dialparties.agi: Starting New Dialparties.agi
dialparties.agi: Caller ID name is 'vega' number is 'vega'
> dialparties.agi: USE_CONFIRMATION: 'FALSE'
> dialparties.agi: RINGGROUP_INDEX: ''
dialparties.agi: Methodology of ring is 'ringall'
Maybe ‘TELC’ is not the string FreePBC is expecting to parse as CallerID?