1. Brekeke Product Name and Version:
Brekeke SIP Server
3.9.4.3/517-1
2. Java version: 1.8.0_231 64-bit
3. OS type and the version: Windows 2008
4. UA (phone), gateway or other hardware/software involved: N/A
5. Your problem:
This works to allow calls from a single caller ID to route how I want it to:
Matching Pattern
$request = ^INVITE
To = sip:(.+)@
$getUri(From) = sip:(<insert 10 digit caller ID here))@(.+)
$addr = 192.168.blah.blah
My question is this -- Can I have a single SIP Dialing Plan rule that allows me to specify a list of Caller IDs so that if an outbound call from my contact platform has one of these Caller IDs, it will Match on this rule and go out a deploy pattern I specify?
Or, if I have ten caller IDs it could be, I need ten dial plan rules?
I know this won't work:
Matching Pattern
$request = ^INVITE
To = sip:(.+)@
$getUri(From) = sip:(<insert 10 digit caller ID here))@(.+)
$getUri(From) = sip:(<insert different 10 digit caller ID here))@(.+)
$addr = 192.168.blah.blah
It actually caused NO outbound call from either 10-digit number to match on this rule.
Thank you!
Brekeke SIP Server
3.9.4.3/517-1
2. Java version: 1.8.0_231 64-bit
3. OS type and the version: Windows 2008
4. UA (phone), gateway or other hardware/software involved: N/A
5. Your problem:
This works to allow calls from a single caller ID to route how I want it to:
Matching Pattern
$request = ^INVITE
To = sip:(.+)@
$getUri(From) = sip:(<insert 10 digit caller ID here))@(.+)
$addr = 192.168.blah.blah
My question is this -- Can I have a single SIP Dialing Plan rule that allows me to specify a list of Caller IDs so that if an outbound call from my contact platform has one of these Caller IDs, it will Match on this rule and go out a deploy pattern I specify?
Or, if I have ten caller IDs it could be, I need ten dial plan rules?
I know this won't work:
Matching Pattern
$request = ^INVITE
To = sip:(.+)@
$getUri(From) = sip:(<insert 10 digit caller ID here))@(.+)
$getUri(From) = sip:(<insert different 10 digit caller ID here))@(.+)
$addr = 192.168.blah.blah
It actually caused NO outbound call from either 10-digit number to match on this rule.
Thank you!