Call connection rule to forward to voxalot URI
 

Whenever I try to create a "call connection rule" that forwards to a voxalot SIP URI, it says the URI is invalid.

e.g.

sip:xxxxxx@us.voxalot.com

where xxxxxxx is a known voxalot id different from the one that this call connection rule is being entered in. Voxalot claims this is "invalid" while

sip:xxxxxx@us.vxalot.com

is "valid" (of course it's not, since it's just a misspelling of voxalot, but that shows that the format is perfectly ok).

Is there a way to have a connection rule forward to a voxalot URI?

Call connection rules not applied to inbound URI
 

If a voxalot account receives and incoming SIP call (e.g. it's sip URI sip:xxxxxx@us.voxalot.com is dialed) it does not attempt to apply the call connection rules.

Is this something requiring a feature request?

forward via sipbroker does the trick
 

Ok, I found a way to forward to another voxalot account. I used this and it worked:

sip:*010XXXXXX@sipbroker.com

where the XXXXXX is the voxalot account ID. It probably does all kinds of bouncing packets around but it works.

Two years after you posted this, I suddenly had a need to do the very same thing, so - Thanks!