Use of # in dial plan and registration

[affinity]

Well you do need a valid number after the stripping of the #1 ... perhaps 12345678 is not valid. I guess you are actually calling a suitable number, no need to confirm. I still think it _might_ be the ATA.

[david]

For what its worth, I use # in my dial plan and it works fine.

I have something like this in Voxalot:

_#3xx. ${EXTEN:2}

Then in my sipura, I have a section of my dial plan that looks like this:

<#3,:#3>xx.<:@gw4>

So when I dial #3, I get another dialtone, and then enter my number. The number gets sent out with a #3 prepended through gw4 (voxalot).

[Tranworld]

Then I don't know why in my case it did not work, yes 12345678 is just a fictitious number, in Singapore telephone have 8 digits, both fixed line such as 62445672 or mobile 96877782 for example, so I would dial #196877782 in the case where my pattern is _#1xx. and 0065${EXTEN:2} (I need to append the prefix for the VSP I used, even for local calls)

but if my dialplan is _1xx. and 0065${EXTEN:1} and I dial 196877782 the it all work.

I know that it should work in both case but it doesn't in the former and does in the latter.
Note that this behaviour is also relevant when I use my Nokia E61 which does not go via any ATA

[martin]

I also have an E61, and thought I'd check what is happening in this scenario. As it turns out, the E61 is sending:

%231

instead of

#1

Note: 23 is the hexadecimal ascii code for #

I suspect that some other devices must be doing this also. I will discuss with the team the possibility of making a change in our system to handle %23 within the number.