Callerid lost when routing via PP?

(1/4) > >>

codex22:
Hi folks,

new to Obi, I'm trying to route calls that come in on the LINE port on one OBI (A) to another OBI (B) to let the phone ring there.

It's working, but I always get the OBI (A) caller id, not the original caller id coming from the LINE port. The caller id is recognized, as I can see it both on a phone connected to OBI (A) and the call logs on OBI (A).

My POTS line InboundCallRoute looks simply like that:

{ph,pp(ob200265443)}

I also tried pp($1>ob200265443) and even pp(123456>ob200265443), but it seems there is never any caller id transported via pp!

Am I doing something wrong or is this just not supported?

Thanks

Michael

yhfung:
You are not allowed to pass the user-defined ID to other end via ObiTalk. Only the OBi number of your OBi device will be passed to other OBi device.

YH

codex22:
YH,

thanks for your fast response.

Quote from: yhfung on May 11, 2011, 08:51:03 am

You are not allowed to pass the user-defined ID to other end via ObiTalk. Only the OBi number of your OBi device will be passed to other OBi device.


That's unfortunate, as this mean I will never know who's calling before I pick up the phone. Can this be done using SIP instead of ObiTalk? Had hoped I could avoid all that.

Michael

yhfung:
Michael，

You may use SP1 or SP2 to pass your defined callerID provided that your SIP service providers allow you to do so otherwise it is the same as OBiTalk.

YH

jimates:
I have multi Obi setup with calls forked to 2nd obi and I wish the incoming call caller id would be passed by the Obi.

Navigation

[0] Message Index

[#] Next page