VOIPTalk.org

[Ray Klassen]

I used to be able to use the dial string "0|[1278]XX." in a router to Voiptalk in the uk but now asterisk hangs me up after the '01.' Is there a feature I can turn off? it works with "90|[1278]XX." so I'm not dead in the water

 

[jroper]

can you post some CLI output

Joe

 

[Ray Klassen]

== Manager 'admin' logged on from 127.0.0.1
-- Executing [012@from-internal:1] ResetCDR("SIP/21-08789818", "") in new stack
-- Executing [012@from-internal:2] NoCDR("SIP/21-08789818", "") in new stack
-- Executing [012@from-internal:3] Wait("SIP/21-08789818", "1") in new stack
-- Executing [012@from-internal:4] Playback("SIP/21-08789818", "silence/1&cannot-complete-as-dialed&check-number-dial-again|noanswer") in new stack
-- <SIP/21-08789818> Playing 'silence/1' (language 'en')
-- Executing [012@from-internal:5] Wait("SIP/21-08789818", "1") in new stack
-- Executing [012@from-internal:6] Congestion("SIP/21-08789818", "20") in new stack
== Spawn extension (from-internal, 012, 6) exited non-zero on 'SIP/21-08789818'
-- Executing [h@from-internal:1] Macro("SIP/21-08789818", "hangupcall") in new stack
-- Executing [s@macro-hangupcall:1] ResetCDR("SIP/21-08789818", "w") in new stack
-- Executing [s@macro-hangupcall:2] NoCDR("SIP/21-08789818", "") in new stack
-- Executing [s@macro-hangupcall:3] GotoIf("SIP/21-08789818", "1?skiprg") in new stack
-- Goto (macro-hangupcall,s,6)
-- Executing [s@macro-hangupcall:6] GotoIf("SIP/21-08789818", "1?skipblkvm") in new stack
-- Goto (macro-hangupcall,s,9)
-- Executing [s@macro-hangupcall:9] GotoIf("SIP/21-08789818", "1?theend") in new stack
-- Goto (macro-hangupcall,s,11)
-- Executing [s@macro-hangupcall:11] Hangup("SIP/21-08789818", "") in new stack
== Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/21-08789818' in macro 'hangupcall'

 

[jroper]

Hi

What I really wanted to see was the number you actually dialled (changed for privacy reasons) and the number that was actually delivered to Voiptalk.

Am I right in saying that they require the call in IETF format e.g. UK landline would equal 441. or 442.

I would do it in a slightly different way to you -

I would have something like 44+0|Z. in your Voiptalk trunk which strips off the leading 0 and prepends 44 only if the second number is not 0. otherwise it will leave it as it is.

If you wanted International Calls through this trunk, you would put:-

00|. which would match anything which began 00 and strip off the leading 00.

In your Outbound route, you will need something like 0[1278]. which would match 01.- UK landline 02.-UK Landline 07.-UK Mobiles (watch out for 070. they are expensive) and 08. UK NGN's

If you wanted to deliver international calls via this route as well, then simply add 00.

So as a general rule, put the modifications to numbers in the trunk to suit each service provider, and use the outbound route simply to select the appropriate route, the exception being where you are using things like 9 for an outside line or other digits to force particular trunks, then you would remove the prefix before it gets to the trunk.

Let me know how you get on.

Joe

 

[Ray Klassen]

well the problem seemed different than all that. As soon as I dialed 012 asterisk grabbed the call and tried to process it before I even got to the rest of the number. Normally I would have thought that that was the phone sending the number before I hit send, but I know I've had the exact same config working on this phone before.

the dial strings work just as you would expect if I add a 9 to the throw-away numbers before the '|' but if I just use a 0 not a 90, that weird behavior ensues.

 

[jroper]

Hi

Can you give a full CLI output for the call - edit the actual numbers dialled for privacy.

What happens if you dial the number, then press send.

Additionally, what happens if you use another phone type, such as Zoiper, where you dial the number, then send it.

Joe

 

[Ray Klassen]

I don't even get to send. what I sent you was all that ever happens. 0-1-2-click-busy . even debug level 10, I get no more than I posted already.

 

[jroper]

Hi

In which case, my suspicion is the phone, although it has worked properly before, where the dial string 012 is triggering send, where 9012 is not - is this the same with all numbers dialed, such as calls to mobiles

Have you got any dial plans setup in the phone.

Can you test with another phone type, eg softphone.

Joe

 

[integrus]

You don't have "early dialing" truned on and have a dial rule that matches 012 by any chance? Check out the link below for more info. Hope this helps.

Regards, Mark.

http://www.ukvoiptalk.com/forum/uk-telecom-voip/22314-asterisk-post-dialling-delay-2.html