Inbound call routing issue: $1 not working

<< < (2/3) > >>

QBZappy:
joshhighley

Hi

This is how I setup my outgoing CID number using Voip.ms. Find the "General Tab" here:

Main Menu>Account Settings>General.

See Image



Edit: The CID number from the Voip.ms General Tab works to replace/override the voipms DID # on the CID.

QBZappy:
joshhighley,

Hi
I don't know if we have exactly the same setup. I tried to reproduce your CID number senario.

Your original setup: (Your first example {ph,SP2($1 > 5555555555)} then you dropped the $1 correct?)
{ph,SPx(>5555555555)}

obi-support2 setup:
{ph,SPx(55555555555)}

Which one did you use?

joshhighley:
QBZappy:  {ph,SP2(55555555555)}

obi-support:  my understanding from the voip.ms website was that if I populated the number on the General tab, then voip.ms would ignore any id coming from the obi.  However, I don't think I had enabled the spoof option before I tried it, so I'll give it another go.

Also, why didn't my use of $1 work?  The obi admin guide documentation makes it seem like it should have worked.

joshhighley:
obi-support:  I put my number back in the voip.ms web panel configuration (General tab), but that seems to keep the obi from overriding the caller number with the inbound call routing rule discussed above.  I think my last resort may be to modify the outbound call routing to pass my caller number using (1111111111>sp2). 

joshhighley:
I think I have it working like I want:  in order to get my caller number to appear on outbound calls, I had to modify the outbound call route for the phone port -- not very clean, but it seems to work.  I modified the **2 rule:

{(<**2:>(Msp2)):sp2(1112223333>)}

where 1112223333 is my phone number.  I tried putting $2 after the > but it then passed the **2 with the number I dialed, so I got a 'not a valid number' error message.  Per the admin guide on page 116, I think the **2 should have been removed from $2 by the rule.  Also, it says not putting the target after the > implies $2, but it obviously works differently when the $2 target isn't explicitly there (it doesn't pass the **2).

For completeness sake, to recap:

my inbound call route for SP2 is {ph,SP2(5555555555)} where 5555555555 is my cell phone that I want to ring simultaneously.  I removed the caller id from the voip.ms web panel General tab so that voip.ms would honor the 'from' number that the obi passes them.  Finally, I had to enable the option X_SpoofCallerId for SP2.

Based on my interpretation of the admin guide, I really think $1 and $2 are *not* working properly.

Navigation

[0] Message Index

[#] Next page

[*] Previous page