support

speeddial via outbound route?

jlutes
Posts: 22
Member Since:
2007-01-09

I have a location that constantly calls one area code. I tried to create a new outbound route to cut down on the number of digits they have to dial as well as allow security to be added if needed. I used the following:

555|+1785nxxxxxx

but all I get back is cannot be compleated as dialed. The log files don't seem to be much help but here are it is:

Aug 8 08:03:49 VERBOSE[22930] logger.c: == Spawn extension (from-internal, 5555551212, 6) exited non-zero on 'SIP/8199-0a06f858'
Aug 8 08:03:49 VERBOSE[22930] logger.c: -- Executing Macro("SIP/8199-0a06f858", "hangupcall") in new stack

Have I just fubar'd the dial pattern? I have never tried to prepend digits but what I have found says that should work...



wcg
Posts: 114
Member Since:
2008-03-12
I think your rule may be wrong

555|+1785nxxxxxx

does not read correctly, as this means when you get a match for 5551785[1-9] (plus 6 more digits) then take off the 555 and add on nothing (as you add the characters to the left of the + sign.

I assume you are wanting to replace 555 with 1785? if so try:

1785+555|nxxxxxx

Let me know if this works.

J



jlutes
Posts: 22
Member Since:
2007-01-09
Not it

Well, I have tried the following with the attached results:

1785+555|nxxxxxx
1785+555|.
Spawn extension (from-internal, 5554339999, 4) exited non-zero on 'SIP/8199-0a069828'

555|1785+.
Spawn extension (from-internal, 5554339999, 4) exited non-zero on 'SIP/8199-0a018588'

1+785nxxxxxx
Spawn extension (from-internal, 7854339999, 6) exited non-zero on 'SIP/8199-09f3db70

What the heck am i missing? I want to dial a 3-digit code followed by a 7-digit phone number and I really don't care if that code is the area code I want to use. The reason I need this configured is to allow a pin set to call one area code.



wcg
Posts: 114
Member Since:
2008-03-12
trunk or route?

Is this rule on the outbound route or on the trunk?

I have this exact rule on a trunk - works fine:

441+901|XXXXX.

Pls advise.

J



jlutes
Posts: 22
Member Since:
2007-01-09
route

I'm trying to do this on an outbound route as the trunk itself is used for multiple routes.

So your rule adds 441 and removes 901 from the dialed string, correct?



wcg
Posts: 114
Member Since:
2008-03-12
ahh - there's the problem!

you can only ADD digits as part of a TRUNK dial pattern rule, you can chop digits off at this point but the primary reason for these patterns is to match a number with a trunk.

here is quite from an article you may find useful:

"Route Dial Patterns cannot be used to add digits to the number dialed by the user. However, you can strip off leading digits before passing them to a trunk. This is most useful if you use a specific dialing code to access a particular route (for example, "9" to access an outside line)."

see:

http://www.aussievoip.com.au/wiki/Hints+on+Route+Dial+Patterns+an...

You may have to create a new trunk then - or you could use impossible characters *** or similar?

btw - yes that was what my rule was doing.

I've not used pin sets, so can't advise on that side of things, sorry :(

J



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.