Dial Plan: Embedded Spaces?

Is there any downside to pasting my dial plan into a SPA3102's
"Dial Plan" field like this:

(
911<:@gw0>S0 |
1800xxxxxxx<:@gw0>S0 |
1855xxxxxxx<:@gw0>S0 |
1866xxxxxxx<:@gw0>S0 |
1877xxxxxxx<:@gw0>S0 |
1888xxxxxxx<:@gw0>S0 |
<:1>800xxxxxxx<:@gw0>S0 |
<:1>855xxxxxxx<:@gw0>S0 |
<:1>866xxxxxxx<:@gw0>S0 |
<:1>877xxxxxxx<:@gw0>S0 |
<:1>888xxxxxxx<:@gw0>S0 |
1xxx[2-9]xxxxxxS0 |
<:1>[2-9]xx[2-9]xxxxxxS0|
011[2-9]x.
)

Instead of this:

(911<:@gw0>S0|1800xxxxxxx<:@gw0>S0|1855xxxxxxx<:@g w0>S0|1866xxxxxxx<:@gw0>S0|1877xxxxxxx<:@gw0>S0|18 88xxxxxxx<:@gw0>S0|<:1>800xxxxxxx<:@gw0>S0|<:1>855 xxxxxxx<:@gw0>S0|<:1>866xxxxxxx<:@gw0>S0|<:1>877xx xxxxx<:@gw0>S0|<:1>888xxxxxxx<:@gw0>S0|1xxx[2-9]xxxxxxS0|<:1>[2-9]xx[2-9]xxxxxxS0|011[2-9]x.)



Seems like the first format is easier to read in the backup copy
and less error-prone.
--
PeteCresswell

"(PeteCresswell)" <x@y.Invalid> wrote in message news:p6l5m6hjdkkbtctjhq18lsv5n24h5bb8l8@4ax.com...
> Is there any downside to pasting my dial plan into a SPA3102's
> "Dial Plan" field like this:
>
> (
> 911<:@gw0>S0 |
> 1800xxxxxxx<:@gw0>S0 |
> 1855xxxxxxx<:@gw0>S0 |
> 1866xxxxxxx<:@gw0>S0 |
> 1877xxxxxxx<:@gw0>S0 |
> 1888xxxxxxx<:@gw0>S0 |
> <:1>800xxxxxxx<:@gw0>S0 |
> <:1>855xxxxxxx<:@gw0>S0 |
> <:1>866xxxxxxx<:@gw0>S0 |
> <:1>877xxxxxxx<:@gw0>S0 |
> <:1>888xxxxxxx<:@gw0>S0 |
> 1xxx[2-9]xxxxxxS0 |
> <:1>[2-9]xx[2-9]xxxxxxS0|
> 011[2-9]x.
> )
>
> Instead of this:
>
> (911<:@gw0>S0|1800xxxxxxx<:@gw0>S0|1855xxxxxxx<:@g w0>S0|1866xxxxxxx<:@gw0>S0|1877xxxxxxx<:@gw0>S0|18 88xxxxxxx<:@gw0>S0|<:1>800xxxxxxx<:@gw0>S0|<:1>855 xxxxxxx<:@gw0>S0|<:1>866xxxxxxx<:@gw0>S0|<:1>877xx xxxxx<:@gw0>S0|<:1>888xxxxxxx<:@gw0>S0|1xxx[2-9]xxxxxxS0|<:1>[2-9]xx[2-9]xxxxxxS0|011[2-9]x.)
>
>
>
> Seems like the first format is easier to read in the backup copy
> and less error-prone.
> --
> PeteCresswell

I certainly keep variants of my dial plan stored as text documents with each functional element on a
separate line, exactly as in your example.

It has never occurred to me to paste them into the dialplan field without painstakingly removing CRs
But now I have tried it I see it seems to works flawlessly despite it putting spaces where the CRs were.

--
Graham.

%Profound_observation%

Per Graham.:
>I certainly keep variants of my dial plan stored as text documents with each functional element on a
>separate line, exactly as in your example.
>
>It has never occurred to me to paste them into the dialplan field without painstakingly removing CRs
>But now I have tried it I see it seems to works flawlessly despite it putting spaces where the CRs were.

I'm thinking in the context of compiler, no run-time errors....

....and something just silently going South at some random time.

Couple people chime in that they've been doing it for years with
no problem and I'll become a believer.
--
PeteCresswell

"(PeteCresswell)" <x@y.invalid> wrote:
> I'm thinking in the context of compiler, no run-time errors....
>
> ...and something just silently going South at some random time.

I just have a shell script:

#!/bin/sh
echo -n '('
echo -n '999S0'
echo -n '|00<:@gw1>'
echo -n ')'

(or whatever, syntax is probably wrong)

Then just cut and paste the output into the web config form.
(Even better, pipe the output to something that will do the 'cut' for me.
xcb might do it)

Theo

In article <gjz*Dqpwt@news.chiark.greenend.org.uk>,
Theo Markettos <theom+news@chiark.greenend.org.uk> wrote:
> #!/bin/sh
> echo -n '('
> echo -n '999S0'
> echo -n '|00<:@gw1>'
> echo -n ')'

Perhaps this would be slightly easier?

#! /bin/sh
tr -d '\n\t ' <<EOF
(
999S0
|00<:@gw1>
)
EOF

- river.