Accessing the call log remotely

<< < (6/6)

Milos:
I have an update to this issue. I went to Europe for Christmas and I was able to fix everything. I now fork calls to my European apartment to my cell phone in the US and to another OBI110 unit in my house in the US. Now OBI110 in my house in the US shows in its call log the caller ID of the caller. This is exactly what I wanted. I did need a second OBI110 for this solution, but it was worth it since if I miss the call, I can always find out who called me.

Thanks guys for all the help.
Milos

Milos:
I forgot to mention that I confirmed that two OBI110 units connected to the same router did not work properly. It was my mistake in the first place that I thought I needed two OBI110 units, since one unit was able to do everything I wanted anyway, so the second unit was not needed and I removed it. I should have read the manual more thoroughly.

Milos

Milos:
Hi,

I have another issue with forking I need help with. On my European OBI110, I fork calls from Europe to my US cell phone and my US OBI110, and that works great. On my US OBI110 I see caller IDs of all  callers. Now, I also wanted to do the same forking with my European cell phone. So I installed OBI202 with OBIBt and connected it to my European cell phone. If I forward calls only to my US cell phone, everything works great. If I fork calls to both my US cell phone and US OBI110, I experience a problem. Namely, my US cell phone usually rings once, sometimes twice, and then the call gets terminated and the cell phone ringing stops. I do see the caller ID of the caller on my US OBI110, but I cannot answer the call using my US cell phone, which is actually my main goal.
I wonder if anybody might know why OBI110 and OBI202 act differently. The InboundCallRoute parameters are identical for both, except that I fork the LINE PORT on OBI110 and ObiBluetooth 1 on OBI202.

Thanks

Navigation

[0] Message Index

[*] Previous page