How to configure the OBi202 with 2 Google Voice numbers?
ianobi:
jimates,
I think we are on the same page here! What you have is RonR’s super-deluxe version where any of 99 Obi devices can all dial through each other and use any trunk on any one of those devices. A total work of art 8)
My suggestion is cut down to suit slightly different needs. If I understand correctly, calls coming in from 290xxxxx1 should use sp1 and calls coming in from 290xxxxx2 should use sp2. A cot type UserDefinedDigitMap would not be useful as we want the two CallerIDs to behave differently (except for calls to aa). Breaking my suggestion down:
{(290xxxxx1)>(Msp1):sp1},{(290xxxxx2)>(Msp2):sp2},{(290xxxxx1|290xxxxx2):aa},{ph,ph2}
If the CallerID is 290xxxxx1 and the number matches a rule in Msp1, then that call will be routed out via sp1.
If the CallerID is 290xxxxx2 and the number matches a rule in Msp2, then that call will be routed out via sp2.
If the CallerID is 290xxxxx1 or 290xxxxx2 and there is no number or no number that matches Msp1 or Msp2, then the call will go to aa.
All other calls ring phone1 and phone2.
Barrt does not need to prepend any trunk designation because the CallerID is telling the Obi202 where to send the call.
Barrt has gone very quiet :-\
ianobi:
jimates,
Your edit crossed with my post. Your Incoming CallRoute is even begining to scare me now :D I think the limit is 512 characters, but I don't want to test that! I suggest barrt tries my way first as it is a bit easier to understand (assuming that it works).
As a more general question, converting RonR's single stage design to suit two cots that route differently would be a challenge! I'm off for two weeks holiday tomorrow; maybe I will think about it after my brain is well rested :)
jimates:
OK. That is really pretty simple isn't it. And it does exactly what bartt wants.
But we know once they get it working they always want more. What about this crude one. With this directing calls to the SP, does it still process through the Mspx for validity?
{(290xxxxx1)>(xx.):SP1},{(290xxxxx2>(xx.):SP2},{(290xxxxx1)>(<**2:>xx.):SP2},{(290xxxxx2)>(<**1:>xx.):SP1},{(290xxxxx1|290xxxxx2)>(<**3:>xx.):SP3},{(290xxxxx1|290xxxxx2)>(<**4:>xx.):SP4},{(290xxxxx1|290xxxxx2):aa},{ph}
But I really would like to know what changes to make to my super-deluxe version to make my apps use their own default line.
I dug this up in my files, it was my original ICR and it worked great for all apps using the same default line.
{(290xxxxxx|290xxxxxx|290xxxxxx)>(xx.):SP1},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**2:>xx.):SP2},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**8:>xx.):LI},{(290xxxxxx|290xxxxxx|290xxxxxx):aa},{ph}
ianobi:
Quote
{(290xxxxx1)>(xx.):SP1},{(290xxxxx2>(xx.):SP2},{(290xxxxx1)>(<**2:>xx.):SP2},{(290xxxxx2)>(<**1:>xx.):SP1},{(290xxxxx1|290xxxxx2)>(<**3:>xx.):SP3},{(290xxxxx1|290xxxxx2)>(<**4:>xx.):SP4},{(290xxxxx1|290xxxxx2):aa},{ph}
This would work, but as you observe no processing through the relevant Mspx would take place. To make that happen simply replace each xx. rule with the relevant Mspx.
Quote
But I really would like to know what changes to make to my super-deluxe version to make my apps use their own default line.
I think this rule should be doing that:
{(Mcot)>(Mpli):sp1}
Assuming that sp1 is your Phone Port PrimaryLIne
Quote
I dug this up in my files, it was my original ICR and it worked great for all apps using the same default line.
{(290xxxxxx|290xxxxxx|290xxxxxx)>(xx.):SP1},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**2:>xx.):SP2},{(290xxxxxx|290xxxxxx|290xxxxxx)>(<**8:>xx.):LI},{(290xxxxxx|290xxxxxx|290xxxxxx):aa},{ph}
Nothing wrong with this, but for processing through the DigitMaps xx. should be replaced with Mspx. For the SP1 line xx. could be replaced with Mpli.
Totally out of time here today. Happy to continue in two weeks time :)
bartt:
I'll have gone silent because replies didn't get emailed. Happy to see the discussion upon returning to the forum site.
I'll jump in, in a week and half when I return from a trip.
Navigation
[0] Message Index
[#] Next page
[*] Previous page