On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT
OBi2182
OBi1022
Poly D230
OBi200
OBi202
OBi212
OBiWiFi5G
Started by LTN1, April 01, 2020, 06:49:07 PM
Quote from: Taoman on April 01, 2020, 07:21:34 PMI'll tell ya if you tell me why you want to do this. What happens when you put the following in your InboundCallRoute?{(<:*GVNUMBER*>xx.):ph}
Quote from: Taoman on April 01, 2020, 11:13:32 PMHmm. Tried it a couple more times on 2 different numbers/SPs on 2 different OBi ATAs and it worked. You're positive the syntax is correct and that's the only thing you have for InboundCallRoute? It really should work. When I tried it the second time it wouldn't even ring but I had forgotten the beginning curly bracket.{(<:*GVNUMBER*>xx.):ph}
Quote from: LTN1 on April 01, 2020, 09:13:56 PMI have daughters that share the same handset connected to the OBi and want to differentiate the incoming call.
Quote from: Taoman on April 02, 2020, 08:59:30 AMQuote from: LTN1 on April 01, 2020, 09:13:56 PMI have daughters that share the same handset connected to the OBi and want to differentiate the incoming call.As far as this issue goes, have you tried using distinctive ring patterns for the different numbers?
Quote from: azrobert on April 02, 2020, 08:11:06 PMYou have a couple things wrong with the rule you're using. First GV send an 11 digit callerid with a "+" prefix, so you won't get a match (xx. will not match a "+"). Second you are prefixing the callerid with 10 digits plus 2 stars, so you will end up with a 24 character callerid. Try the following rule:{(<+1xxxxxxxxxx:9163595555>):ph}
Quote from: azrobert on April 02, 2020, 09:09:29 PMDon't you want to see the original inbound callerid? Just add a leading * to indicate the call is from GV.{(<+1:*>xxxxxxxxxx):ph}Some phones won't display special characters, so prefix with 99 or something else.{(<+1:99>xxxxxxxxxx):ph}
Quote from: LTN1 on April 03, 2020, 09:54:25 AMI tried {(<+1:Mary>xxxxxxxxxx):ph} to see if it would pass the "Mary" with the caller ID (haven't tried numbers or special characters) and it just came through as Private.
Quote from: drgeoff on April 03, 2020, 03:14:38 PMQuote from: LTN1 on April 03, 2020, 09:54:25 AMI tried {(<+1:Mary>xxxxxxxxxx):ph} to see if it would pass the "Mary" with the caller ID (haven't tried numbers or special characters) and it just came through as Private.See the first bullet in the list at the bottom of page 197 of the Admin Guide https://www.obitalk.com/info/documents/admin_guide/OBiDeviceAdminGuide.pdfM has a special meaning in digit maps. Try putting the Mary bit between single quotes - 'Mary'. I'm not saying this will work as I have not tried it myself.