How to pass CID when forking a call?

<< < (2/2)

zapattack:
Instead of
{ph1,sp4(6688)}
format,
I used
{ph1},{sp4(6688)}
as shown in example(4) of the admin manual.

azrobert:
Quote from: zapattack on June 17, 2013, 11:52:17 pm

Instead of
{ph1,sp4(6688)}
format,
I used
{ph1},{sp4(6688)}
as shown in example(4) of the admin manual.


Are you sure your example works?
I always thought processing goes left to right and stops with the first matching rule.
Since you're not comparing for anything in either rule all calls will match the first rule and will be routed to ph1.  Processing will then stop and calls will never be routed to sp4.

zapattack:
Of course you are right. I did it
{sp2(xxxxxxx)}, {ph}
and only noticed the forwarding worked (obviously)!
However ui=$1 doesn't have any effect in my situation as I am routing to an OG trunk which has its own CID.

ianobi:
This appears to be a question of format. Using SIP URI format - anything@anywhere - ui=$1 seems to work fine, but without the @ it does not.

With X_SpoofCallerID = unchecked I tested:

Voice Services > SP1 Service > X_InboundCallRoute:
{ph1,sp2(anything@anywhere)}

This gives CallerID of AuthUserName of sp2.


Voice Services > SP1 Service > X_InboundCallRoute:
{ph1,sp2(anything@anywhere;ui=$1)}

This gives CallerID of the original caller.

Looks like spoofing can be done with With X_SpoofCallerID = unchecked, but only if SIP URI format is used. Another lesson learnt   :)

Navigation

[0] Message Index

[*] Previous page