Code: Select all
sys.Dial("your_provider")
Code: Select all
sys.Dial("your_provider")
Code: Select all
(*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)
Code: Select all
(<:61>13[1-9]xxxS0|<:61>1[38]00xxxxxxS0|<:02>[2-9]xxxxxxxS0|0[12378]xxxxxxxxS0|0[4]xxxxxxxxS0|77[1-9]S0|1[258]1S0|888xxxxxx.S0|000S0|1223S0|0011xx.S0|1900xxxxxx!|<#9:>xx.<:@gw0>|[*x]x.)
Code: Select all
(<:61>13[1-9]xxxS0|
<:61>1[38]00xxxxxxS0|
<:02>[2-9]xxxxxxxS0|
0[12378]xxxxxxxxS0|
0[4]xxxxxxxxS0|
...
0011xx.S0|
1900xxxxxx!|
<#9:>xx.<:@gw0>|
[*x]x.)
There is no equivalent because it doesn't make sense for a SIP server. With a phone/ATA you enter one number at a time and at some point the phone decides to place the call and initiates the SIP call request to the server. With a server there is no concept of a number being entered one digit at a time instead the server has the whole destination straight away.So what is the equivelant of "x.S0" (Wait for numbers, 1 second pause, Dial!).
The closest thing would the SIPSorcery SimpleWizard dialplan. With SimpleWizard dialplans you can create a series of rules that match a call prefix or an exact destination, do some manipulation of the number if required and then forward it to your provider of choice.Okay, so are there any resources available to convert any of my current dial plans into EXTEN compatible or RUBY compatible dial plans (or whatever it is you recommend)?
Code: Select all
case req.URI.User
when /^13\d{4}/ then sys.Dial("61${EXTEN}@some_provider")
else sys.Dial("${EXTEN}@some_other_provider")
end
It was more to add some data - as Voxalot had these same Dialing Rules (obviously "Rules", not "Dial Plans", sorry for throwing that word around.) and when the pattern is matched "________" it would use Provider 1/2/3/4/5 etc.Aron wrote:There is no equivalent because it doesn't make sense for a SIP server. With a phone/ATA you enter one number at a time and at some point the phone decides to place the call and initiates the SIP call request to the server. With a server there is no concept of a number being entered one digit at a time instead the server has the whole destination straight away.
The rule examples seemed to be for a Linksys ATA such as a PAP2. The rules in your ATA don't translate as easily to sipsorcery as your Voxalot rules would have. in fact at the time Voxalot shut down I wrote a migration utility for Voxalot users that converted their rules into the sipsorcery format.Flip wrote:However to program Voxalot, it used a fairly simple interface to just enter details and choose which Account was destination (via drop down - not entering name). i.e. If name of account was changed, no need to update all dial plans! (Feature Request!)/quote]
The sipsorcery SimpleWizard dialplan does allow you to choose your provider from a drop down. In fact the SimpleWizard was designed to be somewhat familiar to Voxalot users since it was deployed around the same time Voxalot shut down. I'll add the feature to update the SimpleWizard "Dial" rules when the provider name changes.
Flip wrote:Okay, maybe that's what we were misunderstanding (you said that device has dial plan stored, not SipSorcery), what I have used before was having the dialling rules built into the VSP (Voxalot / Ayagy) interface which allows you to program each SIP provider to be used when a dialled rule is matched (e.g. for International calls use A, for Mobile calls use B, for Local calls use C, for National calls use C....).
Yep both your patterns are correct.Flip wrote:Okay, if this /^13\d{4}/ is for 13xxxx , then what would it be for 1[38]00xxxxxx?? ([38] = 3,8 (3 or 8.))??
/^1[38]00\d{6}/
What would it be for 1[3-8]00xxxxxx?? ([3-8] = 3 to 8 (3,4,5,6,7,8.))
/^1[3-8]00\d{6}/