Skip to main content

Followme Feature

Posted by ipfreely on Mon, 01/21/2008

Hi All,

Under the followme heading, has anyone used the following?

"Use original caller's Caller ID when forwarding"

Is it working?

I am able to post caller ID info to the PSTN by manualling entering the info, but with this option checked It is just posting the tenant's CallerID

Thanks,
Chris


Submitted by mattdarnell on Mon, 01/21/2008 Permalink

I was able to duplicate your findings.

"Use original caller's Caller ID when forwarding"

Works with Call Forwarding Always, but not with Find Me Follow Me

-Matt

Submitted by sdennis on Mon, 01/21/2008 Permalink

I have also noticed this problem. When using follow me with specific numbers to forward.

Submitted by mattdarnell on Tue, 01/22/2008 Permalink

I would not think it would be a hard fix for Alex....probably just change one variable, just need to know which variable!

Have you tried to contact him to see if he can pump out a quick fix?

I am assuming a customer is breathing down your neck.

-Matt

Submitted by mattdarnell on Fri, 01/25/2008 Permalink

FMFM calls the tl-dialout-base script. It doesn't look like it checks to see if the use original caller-ID variable was set. The original caller-ID would have to be stuffed into a global variable or passed to this script & then it could query if that variable is set.

;; check which caller id to use - tenant/company level or individual

exten => s,n,Set(CALLERID(name)=${DB(TL/TENANT/${tenant}/calleridname)})

;;; if not multi-tenant - bypass some code

exten => s,n,GotoIf($["${tenant}" = ""]?calleridallowed)

exten => s,n,Set(temp=${DB(TL/TENANT/${tenant}/allowaccountcode)})

exten => s,n,GotoIf($["${temp}" != "0"]?accountcodeallowed)

exten => s,n,Set(CDR(accountcode)=${DB(TL/TENANT/${tenant}/accountcode)})

;; set using tenant level caller id

exten => s,n(accountcodeallowed),Set(CALLERID(num)=${DB(TL/TENANT/${tenant}/callerid)})

;; now check if override is allowed

exten => s,n,Set(temp=${DB(TL/TENANT/${tenant}/allowcallerid)})

exten => s,n,GotoIf($["${temp}" != "0"]?calleridallowed)

exten => s,n,Goto(onetrunk,1)

;; individual external caller id

exten => s,n(calleridallowed),NoOp(CLIMYID=${CLIMYID})

exten => s,n,NoOp(MYID=${MYID})

exten => s,n,Set(CLI=${DB(TL/${CLIMYID}/callerid)})

exten => s,n,GotoIf($["${CLI}" != ""]?chkcallfwd)

exten => s,n,Set(CLI=${DB(TL/${MYID}/callerid)})

exten => s,n,GotoIf($["${CLI}" != ""]?chkcallfwd)

exten => s,n,Set(CLI=${DB(TL/TENANT/${tenant}/callerid)})

exten => s,n,NoOp(CLI=${CLI})

exten => s,n(chkcallfwd),NoOp(MYID=${MYID})

exten => s,n,NoOp(INCOMINGCLI=${INCOMINGCLI})

exten => s,n,NoOp(CALLFWD=${CALLFWD})

exten => s,n,GotoIf($["${CALLFWD}" = ""]?setcalleridasabove)

exten => s,n,Set(CDR(accountcode)=${tenant})

exten => s,n,NoOp(CFRETAINCLI=TL/${tenant}${TL_DASH}${ORIG_EXTEN}/CFRETAINCLI)

exten => s,n,GotoIf($["${DB(TL/${tenant}${TL_DASH}${ORIG_EXTEN}/CFRETAINCLI)}" = ""]?setcalleridasabove)

exten => s,n,GotoIf($["${INCOMINGCLI}" = ""]?setcalleridasabove)

exten => s,n,Set(CLI=${INCOMINGCLI})

exten => s,n(setcalleridasabove),GotoIf($["${CLI}" = ""]?nocallerid)

exten => s,n,Set(CALLERID(num)=${CLI})

exten => s,n(nocallerid),Set(temp=${DB(TL/${MYID}/calleridname)})

exten => s,n,GotoIf($["${temp}" = ""]?onetrunk,1)

exten => s,n,Set(CALLERID(name)=${temp})

exten => s,n,Goto(onetrunk,1)

Submitted by thirdlane on Sat, 01/26/2008 Permalink

Guys,

This option gives me a lot of trouble as while people like to see the original caller id it breaks billing and causes confusion - and it seems to be broken.

How important is it for you to have this option? I want to get an opinion whether 1) fix it + allow customers disable it where an arbitrary caller id (of the caller) would not allow the calls go through or it screws up billing 2) Get rid of it alltogether

Please let me know.

Best regards,

Alex

Submitted by eeman on Sat, 01/26/2008 Permalink

Im torn, its nice to be able to pass the number along, but writing out callerid for a number that you dont control or even know it is legit is a slippery slope with the crackdown of callerid spoofing. Then there is the fact that a lot of carriers will strip callerid numbers that arent assigned to a PRI unless you have an agreement otherwise. In other words a PRI that has a bunch of DIDs on it only lets you set callerid on numbers matching those DIDs. I expect this behavior to increase in popularity as the telemarketing crackdowns continue.

Submitted by dozment on Tue, 01/29/2008 Permalink

I will put in a vote to fix it. I need original caller's callerid sent on followme calls.

Submitted by mattdarnell on Thu, 01/31/2008 Permalink

I think it is very nice to have that feature. I like it when I receive calls to my cellular phone. Allows me to call people back if I miss the call.

Would be nice to be able to append digits to the outbound caller ID...let you know if it is a call for AR, AP, support etc.

-Matt

Submitted by eeman on Sat, 02/02/2008 Permalink

FCC requirements are that outbound callerid is exactly 10 digits, no more, no less. Too many complaints for violations can result in a fine to the carrier. Often the carrier will revoke the clients ability to set callerid at all if they refuse to comply. Every time I turn up a PRI I get the same lecture from the carrier about 10 digits and FCC requirements.

in order to append digits one would have to strip digits which more or less makes your callerid useless.

Submitted by George on Sat, 02/02/2008 Permalink

Since we do not use PRIs and are total SIP based this is not a problem for us. Do getting ride of it all together is not an option. for those with a problem (using PRI) if it can't be fixed please allow them to have the option to disable the feature instead.

I would have a LOT of pissed off customers if it were to be removed.

just my 2 cent

G