switched from OBi110 to 200 - autoattendant not working for trusted callers
MikeGJ:
Problem: OBi200 set up out of box doesnt direct trusted callers to autoattendant.
Bought a 200 a while back but was still using 110 with simonics until I started getting "service not configured" errors on outbound calls recently. Decided to set up the 200 - seemed to set up OK, status green and GV on SP1 connected - dashboard has kept both my trusted callers and my speeddial settings from my 110 setup. Set up 200 with my GV account not Simonics (disabled my GV under Simonics account to set up 200).
BUT when I dial in to my GV number from my cell (trusted caller #1) it goes straight through to ringing my house line.
Deleted both trusted callers and put them back - then checked settings under voice services (didnt think to check these untial after I deleted and reentered so I dont know what my settings were defaulted to when I set up the 200).
Thought adding trusted callers AUTOMATICALLY directed those number to autoattendant?
Expert settings for 200 setup shows SP1 X_InboundCallRoute directing trusted callers to aa, entry is {(x.7201234567|x.secondnumber):aa},{ph} - this looks OK to me, but under physical interface Line Port inboundcallroute just shows ph - my 110 settings here show same rule as SP1 X_inboundcallroute.
Anyone have any ideas why this is happening? suggestions welcome.
thanks in advance
azrobert:
Try:
{(@.7201234567|@.secondnumber):aa},{ph}
Edit:
See:
http://www.obitalk.com/forum/index.php?topic=13885.0
If you have a need for a 2nd line, you can use the OBi200 as a GV gateway for the OBi110.
MikeGJ:
thanks for your response - I'd seen another post in day-to-day use regarding the autoattendant not picking up http://www.obitalk.com/forum/index.php?topic=13969.0
and they mentioned something about GV changing its callerID format - they suggested changing x.1 to +1 in the X_InboundCallRoute.
I tried your suggestion of changing x. to @. but all that did was stop my cell ringing the house line instead eventually going to VM.
BUT when I then reverted back to my OBiTalk settings with x.7201234567 and saving, miraculously the next time I tried the AA picked up! Absolutely no idea why - I had tried the other suggestions and reverted back before without success!
UPDATE - ugh. I did nothing else to my settings, just waited while I was typing this, then just tried calling in again from my cell, trusted caller #1 (so SP1 X_InboundCallRoute value is back to x.number) and it rang the phone, AA not picking up!
azrobert:
Use OBi Expert to configure the OBi200. If you use the local interface, OBiTalk will overlay your changes. You need to disable OBiTalk Auto Provisioning to use the local interface, but then you won't be able to make any changes from OBiTalk.
MikeGJ:
thanks again - I am using the expert to make changes - I only use the local to see my call history. It seems I can repeat the AA picking up after reverting but only the first time. Second time I call in AA does not pick up but rings the phone!
So having value set as x.10digitnumber AA does not pick up but rings house line. I've tried setting value to x.1tendigitnumber with no success; oddly using @.tendigitnumber cause the house line not to ring but I hear it ringing on my cell, which then goes to VM.
As I understand it x means any digit 0-9, and @ means any alphanumeric character except #,
so @.7201234567 should match string ending in these ten digits? WHich should work, but then I dont see why 1) it doesnt, and 2) it causes the phone not to ring and instead go to VM.
I've tried twice now, and reverting to the obitalk settings (x.tendigitnumber) after making changes that didnt work has resulted in the next call being picked up by AA, but subsequent calls form the trusted number going straight through and ringing the house line.
If I could figure out how to embed an image I'd show you my call history (clicking on the insert image just puts this code in the text - I dont know what to insert to load an image!) showing the times AA picks up.
Navigation
[0] Message Index
[#] Next page