(2) Obi 202's in one place: Distinctive ring and other questions
infin8loop:
Quote from: ianobi on January 06, 2013, 07:30:56 am
It does seem that the only time OBi#2's number is used in cot is incoming calls on obi#2, line SP2. However, I guess you might use the phone ports on OBi#2 one day, or kids may change their mind about having calls ring through to OBi#1.
You could try replacing {(Mcot):aa} with {(Mcot)>**0:aa}
This requires users within cot to send **0 to access aa, the same as dialling from the local phone port. All other calls will ring the phone.
You may actually want to replace {(Mcot):aa} with {(Mcot)>*0:aa} in OBiTalk Service InboundCallRoute
This is how I modified Ron's Single-Stage Dialing through any Trunk (using OBiTalk). I route all calls coming into my Obi#2 to Obi#1 to take advantage of the only cordless phone system attached to Obi#1. Without this mod, incoming calls to Obi#2 were ending up in aa on Obi#1. QBZappy might remember this because he discovered it when he called me. I hate it when that happens. In testing I was expecting to end up in aa because my cellphone used to test was in trusted caller (which is different than circle of trust), so I didnt think anything of it.
ianobi:
Good thinking infin8loop :)
A lot of my incoming routes are direct from softphones etc via an SPx where no * is lost. However, using OBiTALK a * is lost on the way from one OBi to another.
Chuck_in_ABQ:
Thanks, Infin8loop. I was thinking someone else had to had this issues, and this makes sense. I did search and find your original post on the issue.
Anyone have thoughts on the dial-out from tablet to voicemail, bridging 2 obi's?
Thanks
Chuck
Navigation
[0] Message Index
[*] Previous page