Modifying Incoming Caller ID Display to Show Which Line Was Called

<< < (2/2)

azrobert:
If you are using Taoman's suggestion, there are potentially 3 problems.

If your service provider includes country code, you need to allow for it in the rule.
{(<1XXX:2***>xx.):ph},{(<1:2*>xxxxxxxxxx):ph}

Anything to the left of the colon is used to match the callerid and is removed upon a match. Anything to the right of the colon is added.

Some phones won't display the callerid if it contains non-digits. Remove the asterisks.

{(<XXX:2>xx.):ph},{(<:2>xxxxxxxxxx):ph}

Anonymous (no callerid) won't ring. You might want this.

My suggestion isn't as sophisticated, but I tried to include all possibilities.

{(<1>x.):ph},{ph}

x. will match zero or more digits, so it will also match anonymous calls and 10-11 digit callerids.
When you are only adding digits, the colon is optional.
I included {ph} just in case the callerid didn't match the 1st rule, the callerid will be unchanged.
I just tested my suggestion on an OBi110 and it worked.
I did a cut and paste from my post.
I don't know why it's not working for you.

Michael_Reeder:
azrobert (and all):

Thanks once again!

Okay - I found the stupid problem.

The problem was having the phone number I was test-calling from programmed into my Panasonic handset phone book attached to the Obi device.  The phone book entry in the handset overrode the changes specified in X_InboundCallRoute, such that:

a. A correct digimap in X_InboundCallRoute resulted in the handset displaying whatever was in the handset phonebook (ignoring X_InboundCallRoute),

b. An incorrect error-filled digimap in X_InboundCallRoute resulted in the handset displaying nothing,

c. Deleting the handset phone book entry for the calling phone number resulted in THIS WORKING FINE! (X_InboundCallRoute specifications being displayed on the handset)
 

So I now have this working on SP1 through SP4.  Yeah!


Riddle me this: (Follow-On Question)

My handset is attached to PH2 on my Obi.

I have learned and removed all testing phone numbers from the handset phone book as well as from my cell phone phonebook.

For BT1 (blue tooth call from my cell phone routed through my Obi):

{(<7*>x.):ph2},{ph2} = The unmodified inbound call ID being shown.  X_InboundCallRoute is ignored.

{(<7*>x.):ph2} = NOTHING being shown on the inbound caller ID on the handset.

This suggests that for BT1 (blue tooth connections) the conditions on the inbound call thru bluetooth are somehow not met in the digimap. ???

Of course - if I have to - I can stop here.  I have a number in front of each SPx line, and inbound caller id without a preceding number is my clue that its a blue tooth call.

-- Michael

azrobert:
Quote from: Michael_Reeder on October 18, 2017, 05:46:45 pm

{(<7*>x.):ph2} = NOTHING being shown on the inbound caller ID on the handset.


{(<7*>x.):ph2}
If "x." doesn't match the callerid then the phone shouldn't ring. I don't understand if it's ringing without callerid.

The only explanation I know is the callerid from BT contains a special character. This character might not be displayable. Try the following:
{(<7*>@.):ph2}

@ will match any character.

Michael_Reeder:
Quote from: azrobert on October 18, 2017, 06:10:24 pm

{(<7*>x.):ph2}
If "x." doesn't match the callerid then the phone shouldn't ring. I don't understand if it's ringing without callerid.

The only explanation I know is the callerid from BT contains a special character. This character might not be displayable. Try the following:
{(<7*>@.):ph2}

@ will match any character.



azrobert -- You nailed it.

Yes - The problem was the special character.

Thanks,
Michael

Navigation

[0] Message Index

[*] Previous page