FollowMe does not seem to send out Clids properly - Missing text

sending out the callerid name is mostly irrelevant when going out a trunk since only the number is transmitted through the pstn. (The only exception might be calling another user who has service with your same voip provider). Otherwise the final pstn connection where the call is being delivered to the recipient provides their own lookup of the name.

We'll review to make sure there isn't something being left off. (Although - I use it extensively and have not noticed anything being left off that is needed).

Actually this isn't true in Canada (which is where I believe pbassel is located). Some Canadian providers pass the CallerID Name out their PRI and it is presented to the recipient. This is different than it is US which only supports CNAM through LIDB.

At least this is my understanding and my experience. I have a Canadian VoIP provider for my Canadian DIDs and a US provider for my US DIDs.

Thanks Rob for the confirmation of the situation. Yes I am in Canada and yes they providers do pass the CIDs. In fact that was part of the point I was making. the text part of CID is being passed on by provider if someone dials my number from and internal extension based on the text CID that I entered into the extension definition page but it is not passed on when the call come from an outside caller.

p_lindheimer, I suspect this is a very small thing to fix but it is beyond my capabilities. If you are able to address this at some point that would be great. Thanks in advance.

One other issue I would like to ask about due to the fact I am in Canada. I can repost this elsewhere, if desired. In any case, it would be great if we could set the default language at the extension level and likely at IVR "levels" or IVR pages on web interface. The reason is that some of my users are in Quebec and they want people who call them to get answered but the system in French. There personal messages are already in French but the system recordings come out in English (as the box is setup in the English part of Canada). To get around this problem we have simply recorded messages "announcements" to be used where the system recordings would normally appear and we are able to get around the issue for about 97% of the time but for that other 3% English system recordings seem to be unavoidable. For myself, as I get calls from English and French callers, I have set up an English extension and a French extension with associated applicable recordings.

One day, it would be great if the caller could be asked what language they want to be served in, then where applicable the system uses the system recordings in that language and then when the call is sent to my phone I the system could send an xml message telling what line they are calling, what department they are calling and what language they want to be served in. I have only Aastra 480i phones and they are supposed to be able to have some xml capabilities, so it would be great if they could be used.

Thanks for all your efforts on this great project (FreePBX).

Regards

Peter Bassel Toronto, Canada

#2324 is a duplicate of this that was reported later and has a log file in it as well.

The following patch should fix it. This patch is generated from svn/head 2.4 but should apply to a 2.3 version. It will be kept in 2.4 only until some testing can be done to role it back to 2.3.

see r5200

Index: etc/extensions.conf
===================================================================
--- etc/extensions.conf (revision 5199)
+++ etc/extensions.conf (working copy)
@@ -992,15 +992,21 @@

 ; If this came through a ringgroup or CF, then we want to retain original CID unless
 ; OUTKEEPCID_${trunknum} is set.
+; Save then CIDNAME while it is still intact in case we end up sending out this same CID
 ;
 exten => s,n,GotoIf($["${KEEPCID}" != "TRUE"]?normcid) ;Set to TRUE if coming from ringgroups, CF, etc.
 exten => s,n,GotoIf($["x${OUTKEEPCID_${ARG1}}" = "xon"]?normcid)
 exten => s,n,GotoIf($["foo${REALCALLERIDNUM}" = "foo"]?normcid) ;if not set to anything, go through normal processing
 exten => s,n,Set(USEROUTCID=${REALCALLERIDNUM})
+exten => s,n,Set(REALCALLERIDNAME=${CALLERID(name)})

 ; We now have to make sure the CID is valid. If we find an AMPUSER with the same CID, we assume it is an internal
 ; call (would be quite a conincidence if not) and go through the normal processing to get that CID. If a device
 ; is set for this CID, then it must be internal
+; If we end up using USEROUTCID at the end, it may still be the REALCALLERIDNUM we saved above. That is determined
+; if the two are equal, AND there is no CALLERID(name) present since it has been removed by the CALLERID(all)=${USEROUTCID}
+; setting. If this is the case, then we put the orignal name back in to send out. Although the CNAME is not honored by most
+; carriers, there are cases where it is so this preserves that information to be used by those carriers who do honor it.
 ;
 exten => s,n,GotoIf($["foo${DB(AMPUSER/${REALCALLERIDNUM}/device)}" = "foo"]?bypass:normcid)

@@ -1015,8 +1021,9 @@
 exten => s,n,Set(CALLERID(all)=${TRUNKOUTCID})
 exten => s,n(usercid),GotoIf($["${USEROUTCID:1:2}" = ""]?report) ; check CID override for extension
 exten => s,n,Set(CALLERID(all)=${USEROUTCID})
-exten => s,n,GotoIf($["x${CALLERID(name)}"!="xhidden"]?report:hidecid) ; check CID blocking for extension
+exten => s,n,GotoIf($["x${CALLERID(name)}"!="xhidden"]?checkname:hidecid) ; check CID blocking for extension
 exten => s,n(hidecid),SetCallerPres(prohib_passed_screen) ; Only works with ISDN (T1/E1/BRI)
+exten => s,n(checkname),ExecIf($[ $[ "${CALLERID(number)}" = "${REALCALLERIDNUM}" ] & $[ "${CALLERID(name)}" = "" ] ],Set,CALLERID(name)=${REALCALLERIDNAME})
 exten => s,n(report),NoOp(CallerID set to ${CALLERID(all)})

 ; Privacy Manager Macro makes sure that any calls that don't pass the privacy manager are presented

Tested = working. manually made the above changes to v2.3.1.3 /etc/extensions.conf

The missing outgoing NameID in RingGroups, Follow me etc. has now been corrected.

Thank You.

thanks, I'm going to have to back off the patch though although will see if I can't make an option to make it optional. There are carriers, both PRI and VOIP who have problems when sending names - in some cases completely rejecting the call.

Currently there is the option in the TRUNK to 'Never Override CallerID'.

If this setting were enabled by default, would that accomplish the requirements of both types of carriers?

Cheers.

no - that will simply block the callerid all together from a forwarded/follow-me call and will result in using the trunk cid setting.

I understand. A switch to enable or disable only the NameID portion.

This should also be set on a trunk by trunk basis, as a user may subscribe to one provider that allows it, and another which would reject it.

at this point it is not going to be set on a trunk by trunk basis. As it stands there are very few providers who do anything with cidname even when you send it to them - in most of the world the information is discarded. When we redo trunks / outbound routes maybe we'll accommodate it on a trunk by trunk basis but not at this point - that old code is just to ugly to keep building on top of for something as obscure as this.

r5575 reverted

revert patch to send cidname - there have been reports that some providers ignore all CID when this is done or even reject calls, and since it is rare that a provider will even look at cidname in most of the world, it has been chosen to go back to previous behavior. If there is enough feedback that an option to have the name sent out is desired, we can look at adding a conifguration switch that would allow it on a given installation

Hi. I will continue to use this patch (I will test it with the latest core 2.3.1.4).

I currently use three different trunk providers (Sasktel, Shaw, evoip) and all of them allow me to send my own CIDname.

My concern is that we plan on adding a forth provider shortly and IF they do not allow us to send CIDname, I will need to find a way to allow the first three to send CIDname, and the forth not to send CIDname.

Cheers,

bct, how are you connecting with Shaw to send CIDname? Do you have an IP trunk to them or using their voice modem? Thanks.

Hi bromont. We have a Full PRI with Shaw, so we can pretty much do anything we want with it.

I will start playing with Shaw Home Phone in the next couple of months, but I anticipate that controlling CIDname is not possible with residential services.

Cheers