Incoming call from sp1(Obi100) by Obitalk forward to another OBi110 !
pc44:
Hi AlexSun,
I'm thinking the X_SpoofCallerID may not work via Obitalk.
Is the Caller ID successfully getting passed to the OBI110? When you look at your Call History on the OBI110, does it list the correct Caller ID for the calls from the OBI100? (I was hoping it was showing you the Caller ID of the original caller that is being forwarded, and I was also hoping for the Caller ID of the OBI100 when you are dialing directly from OBI to OBI).
Not sure on this,
pc44
AlexSun:
Quote from: pc44 on June 24, 2012, 09:41:49 am
Hi AlexSun,
I'm thinking the X_SpoofCallerID may not work via Obitalk.
Is the Caller ID successfully getting passed to the OBI110? When you look at your Call History on the OBI110, does it list the correct Caller ID for the calls from the OBI100? (I was hoping it was showing you the Caller ID of the original caller that is being forwarded, and I was also hoping for the Caller ID of the OBI100 when you are dialing directly from OBI to OBI).
Not sure on this,
pc44
Hello pc44
In call history(Obi110) I saw correct Caller Id (700 123456), but why aa(Obi110) answer this Caller Id? I only set (OBI110 set: OBiTALK Service --- InboundCallRoute: {300333333:aa},{ph}), I can't understand.
Stewart:
An OBiTalk call in essence has two caller IDs -- the number of the sending OBi (used for authentication and routing) and the number of the original caller (to be passed on to the destination phone). The manual doesn't make it clear when and how these are used.
I believe that if on the OBi110, the OBiTalk Service -> InboundCallRoute is {300333333>1:aa},{ph}
and on the OBi100, speed dial 2 is set to pp(200111111)
then you could dial 2*1# on the OBi100 to reach the AA on the OBi110.
Hoever, it may be more convenient to avoid the AA altogether; see http://www.obitalk.com/forum/index.php?topic=1103.0
AlexSun:
Quote from: Stewart on June 24, 2012, 10:37:09 am
An OBiTalk call in essence has two caller IDs -- the number of the sending OBi (used for authentication and routing) and the number of the original caller (to be passed on to the destination phone). The manual doesn't make it clear when and how these are used.
I believe that if on the OBi110, the OBiTalk Service -> InboundCallRoute is {300333333>1:aa},{ph}
and on the OBi100, speed dial 2 is set to pp(200111111)
then you could dial 2*1# on the OBi100 to reach the AA on the OBi110.
Hoever, it may be more convenient to avoid the AA altogether; see http://www.obitalk.com/forum/index.php?topic=1103.0
The problem has been solved, very grateful to Stewart.
Now I fully understand this syntax: {300 333 333> 1: aa}
infin8loop:
Quote from: Stewart on June 24, 2012, 10:37:09 am
An OBiTalk call in essence has two caller IDs -- the number of the sending OBi (used for authentication and routing) and the number of the original caller (to be passed on to the destination phone). The manual doesn't make it clear when and how these are used.
I believe that if on the OBi110, the OBiTalk Service -> InboundCallRoute is {300333333>1:aa},{ph}
and on the OBi100, speed dial 2 is set to pp(200111111)
then you could dial 2*1# on the OBi100 to reach the AA on the OBi110.
Hoever, it may be more convenient to avoid the AA altogether; see http://www.obitalk.com/forum/index.php?topic=1103.0
Using this as inspiration I made a change to the InboundCallRoute as originally outlined in http://www.obitalk.com/forum/index.php?topic=1103.0:
Voice Services -> OBiTALK Service -> InboundCallRoute (OBi100/OBi110):
{(Mcot)>(<*1:>(Msp1)),(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<*2:>(Msp2)),(Mcot)>(<**2:>(Msp2)):sp2},
{(Mcot)>(<*8:>(Mli)),(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<*9:>(Mpp)),(Mcot)>(<**9:>(Mpp)):pp},
{(Mcot)>(Mpli):pli},{(Mcot)>*0:aa},{ph}
I added the 3 characters in red >*0 above. This allows using OBiTalk to forward incoming calls from one OBi to another without them ending up in the AA of the target machine because each Obi is in the COT of the other (the AA issue was luckily discovered by an incoming call from a non-hostile "voip buddy"). My Obi's are numbered 91 and 92 (using the speed dial concept as outline in the referenced post). So I can dial 92**0# from Obi1 to reach AA on Obi2 or 91**0# from Obi2 to reach AA on Obi1. The **0 keeps the spirit of the original dialing method intact as well. For the record I'm not sure if this breaks OBion clients, etc. ability to get to AA. I don't use them..... yet.
I had already come to the same conclusion of "An OBiTalk call in essence has two caller IDs....". I just wasn't sure of a way to get around it until I saw this series of posts. So, thanks!
Navigation
[0] Message Index
[#] Next page
[*] Previous page