[Simon2007]

Hi

I have a set up of:

SPA9000
SPA400
SPA942(s)

Although I am an extreme novice at dial plans, mine seems to work fine for my needs, apart from the following:

My PSTN line is a feature line, where for instance with an ordinary phone plugged into the wall socket you are able to dial *xx* (for example *21*) and have access to a range of features provided by the telephone company.

In this case *21* activates the call divert menu.

With my Sipura equipment conected to the PSTN line (rather than just an ordinary phone plugged into the wall jack), I have a problem dialing out *xx* and also #xx#.

To dial out on pstn via my Sipura equipment, I first of all dial 8
Note: All other outgoing PSTN calls via Sipura equip work fine.

To allow me to dial the *xx*, I added the following to the beginning of my dial plan.

8,*xx*S0|8,#xx#S0|

If I dial 8*21* I end up with a fast busy.

Can anyone advise where I may be going wrong?

The fast busy occurs immediately after dialing the last * or last #

Any help would be fantastic!

Strange as I have a dial plan element 8,1471S0| and this works fine!

[jbear]

Hi,
I suspect your problem lies not with the 942 dial plan but on the 9000
If you have a call routing element something like
<8:L1>xx. or <:L1>8xx. it would not be able to find a line for a number
containing # or *
As far as I am aware, the "," in the 942 dial plan only gives a simulated dial tone while waiting for the next digit. You haven't actually left the phone until you press dial or match an S0 pattern.
Failing this (or in addition to it), have a look at the 9000 outbound dial plan which is probably something like <8:>xx. again not allowing for non-numerics.
Hope this helps.

[Simon2007]

Thank you jbear! I am now 50% there thanks to your help.

Following your recommendation, I changed the SPA9000 dial plan.

For call routing, I changed <:L2>8xx. to:

<:L2>8xx.|<:L2>8[*#]xx[*#]

For the Line 2 tab (the PSTN one) I changed the dial plan to:
(<8:>[*#]xx[*#]|<8:>xx.)

Finally I made sure that the phone dial plan included:
8,[*#]xx[*#]S0

The result is that I can now dial 8*21* to access my feature line features - thank you.

Unfortunately 8#21# still does not work. I get a fast busy after dialing the last #

Its almost as if the # in the dial plans is not recognised. Should I be using a different symbol to allow this to be dialed? Maybe the # is already assigned to another function with Sipura equipment?

[jbear]

Unfortunately I can't help you there (yet). I have the same issue with #21# which is what led me to your thread in the first place.
I hoped at the time that my problem was related to another part of my ridiculously convoluted dial plan and that you would not have it.
I have since done a little more and
where I am up to so far is that a #21# gets out from the phone,
is appropriately routed by call routing and recognised by the outbound line
on the 9000.
I have checked this by putting a dial plan <8#21#:99999999> in the outbound 9000 line where 99999999 is a direct pstn number which rings when you dial the #21#. From this I conclude that the problem lies downstream from there - presumably with the 400.
Anyway that's where I am at the moment, I'll let you know if I solve it before you do. If you get there first please post the soln.
JB

[Simon2007]

Hi Jbear

Did you manage to find a solution to the #21# dial out by PSTN problem?

I have still not managed to dial out #21# successfully

[jbear]

Sorry, haven't had a chance to get back to it yet. I believe it is the # being interpretted as a voicemail instruction by the 400 but beyond that ....
The complaints are getting louder so I'll have to get serious about it soon.

[humba3]

Actually, I use #X is trunk seizure prefixes and that works like a charm. However, I suspect that the reason you cannot conclude a dialling pattern with a # is that the # is interpreted as the send key and thus is never forwarded to the PBX in the first place. You can easily verify that by activating SIP traces on the SPA9000 (ideally on the line connected to your SPA400.. so you'll see what the SPA400 will try to dial on the PSTN line).

Have you tried using the call routing rules on the SPA400 interop line to add a training # to see what happens in that scenario?

Also, I cannot help but think that if you have a PBX, using CO features from your PSTN provider is kinda redundant.. you should control those features on your PBX, not on the upstream provider. Otherwise, you'll get one heck of a mess when the two configurations get out of synch and you never know who is blocking what. If there's an inheritent limit as to what the PSTN line can do (I don't really know.. I've had ISDN for the past 10 years and now only SIP trunks.. ), perhaps a SIP trunk would be more beneficial, as it allows you to set a cfwd on the phone that the call is finally routed to, and that redirect gets back to your IPTSP which then reroutes the call transparently and you don't have to try and teach your users the difference between the cfwd softkey on their phone, and dialling *21* (which then affects all your users, versus cfwd only affecting the phone in question).