how to remove [macro-outbound-callerid] from extensions_additional.conf

How did you correct this context? Or you just delete it? I have the same problem with blank CallerID over IAX2 trunk.

Replying to Oleh:

How did you correct this context? Or you just delete it? I have the same problem with blank CallerID over IAX2 trunk.

For now I just comment out the entire [macro-outbound-callerid] section.

[macro-outbound-callerid]
include => macro-outbound-callerid-custom
;exten => s,1,GotoIf($["${REALCALLERIDNUM:1:2}" != ""]?start)
;exten => s,n,Set(REALCALLERIDNUM=${CALLERID(number)})
;exten => s,n(start),Noop(REALCALLERIDNUM is ${REALCALLERIDNUM})
;exten => s,n,GotoIf($["${KEEPCID}" != "TRUE"]?normcid)
;exten => s,n,GotoIf($["x${OUTKEEPCID_${ARG1}}" = "xon"]?normcid)
;exten => s,n,GotoIf($["foo${REALCALLERIDNUM}" = "foo"]?normcid)
;exten => s,n,Set(USEROUTCID=${REALCALLERIDNUM})
;exten => s,n,GotoIf($["foo${DB(AMPUSER/${REALCALLERIDNUM}/device)}" = "foo"]?bypass:normcid)
;exten => s,n(normcid),Set(USEROUTCID=${DB(AMPUSER/${REALCALLERIDNUM}/outboundcid)})
;exten => s,n(bypass),Set(EMERGENCYCID=${DB(DEVICE/${REALCALLERIDNUM}/emergency_cid)})
;exten => s,n,Set(TRUNKOUTCID=${OUTCID_${ARG1}})
;exten => s,n,GotoIf($["${EMERGENCYROUTE:1:2}" = ""]?trunkcid)
;exten => s,n,GotoIf($["${EMERGENCYCID:1:2}" = ""]?trunkcid)
;exten => s,n,Set(CALLERID(all)=${EMERGENCYCID})
;exten => s,n,Goto(report)
;exten => s,n(trunkcid),GotoIf($["${TRUNKOUTCID:1:2}" = ""]?usercid)
;exten => s,n,Set(CALLERID(all)=${TRUNKOUTCID})
;exten => s,n(usercid),GotoIf($["${USEROUTCID:1:2}" = ""]?report)
;exten => s,n,Set(CALLERID(all)=${USEROUTCID})
;exten => s,n,GotoIf($["x${CALLERID(name)}"!="xhidden"]?report:hidecid)
;exten => s,n(hidecid),SetCallerPres(prohib_passed_screen)
exten => s,n(report),Noop(CallerID set to ${CALLERID(all)})

; end of [macro-outbound-callerid]

The following link has a similar issue which I worked with but it is in reference to v1.2 However, I syspect the fix would be similar:

http://www.freepbx.org/trac/ticket/2191

Again, the major issue that I face now (in v1.4) is that this context is located in extensions_additional.conf, where the [macro-outbound-callerid] context is regularly reset back to it default settings after making any Findme changes, trunk changes, inbound changes etc.

I considered using extensions_override_freepbx.conf but I an uncertain how to use this to exclude (or change) the [macro-outbound-callerid] context.

Thanks.

This bug report/patch report does not tell us anything. Why don't you indicate what the ultimate problem is that you are trying to solve and why it is a problem? What scenario are you not having the CID Name sent and why do you need it sent in that scenario?

CallerID(name) is lost when going over an IAX2 trunk - how do I fix the CallerID(name) over IAX2

After removing the [macro-outbound-callerid] context, all CID works as expected.

Please let me know if additional details are needed. Thank You.

this doesn't tell me any more then you already wrote. What explicitly is the issue? There are very few providers that do anything with CID Name and some who reject the calls if you provide it (which is why it is not in there). You also break quite a bit of functionality and can end up creating other problems if you out-right remove it. So - as requested, please specify what is the ultimate problem that you are running into that you are trying to solve by sending CID Name?

Thanks for your patience. We have two servers connected together using an IAX2 trunk. I am trying to pass CIDname from Server1 to Server2 via the IAX2 trunk.

Server1 has a FULL PRI (Note: we have full control over Name and Number ID) - incoming calls are identified using DID's - specific DID calls that are received on the PRI are being sent to Server2 (via the IAX2 trunk) - these calls are working fine, but only the NumberID is working (not the NameID)

This has two impacts: 1. Anything set in 'CID name prefix' is stripped on Server1 before being sent to Server2 2. The inbound NameID feature from the Telco is also being stripped on Server1 before being sent to Server2… therefore the staff no longer receives this information on an inbound caller.

Cheers.

try setting the trunk to an intra-company trunk and see if that fixes it, although I think it may not. If not, there is another ticket that is closed at this point, with a patch in it (I think I put the patch in it), that patched macro-outbound-callerid, so that it sends the CID Name. You'll have to redefine the entire macro and include that patch, which will override the auto-generated one. As far as setting CIDName on the outbound calls to the PRI, test it to an outside phone and confirm your telco is actually doing something with it - they usually don't/can't but there are some cases that are exceptions.

Thanks p_lindheimer.

I enabled the 'Intra Company Route' feature on Server1's 'Outbound Routes' and the CallerID(name) appears to be working.

I will have to do additional testing next week but so far so good. THANK YOU!

I have used the following patch http://www.freepbx.org/trac/ticket/2191 on older versions (Asterisk 1.2, FreePBX 2.3) before, and it worked perfectly... Fortunately it looks like I will NOT need to patch anything in this setup.

Yes, both our wired Telco PRI and our Virtual PRI Trunks allow us to send any NumberID and NameID. Because we run several corporate identities, this is a requirement for us to have this feature. We have been able to send out any CID information (name & number) for the past 6 months without issue.

Have a great weekend.

closed as there doesnt seem to be an issue