Use of # in dial plan and registration
 

Is the use of the # now not possible? In one of the sticky note, a user have a dialplan which shows _#1xx. {EXTEN:2} which is what I have tried to emulate, however everytime the system would say, "the number dialled could not be completed", it seems only digits are now recognised as removing the # and {EXTEN:1} works OK. I just want conformation of my observation.

As a new user I would like also to ask whether I need 2 accounts to register 2 devices? I have an SMCWTVG ATA which is also a WIFI AP, and I have a Nokia E61 which uses the AP for access, can I set up both the E61 and the SMC device with the same Voxalot account and have them both registered? Seems like a silly request but I am only using the devices to dial out, receiving calls is not used at the moment thus having 2 separate device registrations does not seem imperative (the only reason i want to keep one account is just so that one dialplan can be used)

It could be that your ATA is not passing the #. Some ATA's work fine with 'special' characters like "*" and "#" and maybe even "+", others do not. Some ATA's use ""#" as a terminator to initiate the call.

You can have more than one device registered with the same voxalot account. You cannot SIP register the same provider on multiple clusters though.

If you have multiple devices registered, you should probably use the same cluster for them all. All registered devices ring if there is an incoming call, so that could be good or bad as you see it.

I am using a SMCWTVG which does not use these at all (no dialplan), they just pass through, the problem is immediately where it hits the Voxalot then it seems to baulk, anyway since you think it should work, I will test again.

As far as multiple registration is concerned, that's perfect for my use

Thanks for the reply

Yep I've tested it both with the ATA and with the Nokia E61 and they both have the same response which is from Voxalot, in fact I searched Voxalot tutorial and it all seems to point to # and * not being used at all?

_#1. ${EXTEN:2} VoXaLot
_#1*x. ${EXTEN:2} VoXaLot
_#1**. ${EXTEN:2} VoXaLot

This isn't really a good example, but these three allow all calls via Voxalot such as:

#1853804 to sip:853804@voxalot.com
#1*600 to sip:*600@voxalot.com (voicemail)
#1**2 to sip:**2@voxalot.com (speed dial 2)

Of course these can all be done a little differently and directly:

*061853804
*600
**2

Could it be because of the #1, i.e. you use 2 digits whereas I only use 1?

#. ${EXTEN:1}

Yep I've checked it again, leaving everything the same, I simply add the # in front and modify ${EXTEN:2} and it said "we are sorry the number you've called cannot be connected"

The ${EXTEN:2}in my example, removes the #1 and passes everything else.

Yes I can understand the logic of EXTEN, I have this
_1xx. ${EXTEN:1} which mean the first digit is stripped out then the rest dialled, this worked when I dial 112345678 (it dials 12345678 of course). Then I modify it to be

_#1xx. ${EXTEN:2} then it doesn't work, it should simply strip out the 1st 2 digits and dial the string, but it doesn't ! (I dialled #112345678 of course)