Freephoneline, voip.ms, and googletalk dialplan request

<< < (9/9)

Webslinger:
Quote from: azrobert on December 21, 2014, 07:57:31 am

I'm getting the same quick busy when calling myself, but I can successfully call another OBi ATA.

If my memory is correct in the past you would get a response code 404, which means Not Found and an IVR message saying the call failed. I tried this a long time ago before I had multiple OBi ATAs. Maybe 2 years.



Okay, great, thank you very much. Happy Holidays!

Webslinger:
Quote from: azrobert on December 14, 2014, 11:08:02 am

Try changing rule <00:$1> in the AA DigitMap to: 00

Now 00 will be sent to the AA outbound route.

Then add the following rule to the beginning of the AA outbound route:
{00:sp1($1)},




With your help, I appear to have fixed this issue.

Previously, I had return calls being dialed from SP1 due to **1 being in my inbound call route for SP1: {(<**1>(x.1234567890|x.2345678901)):aa($1)},{ph,ph2}

**1 showing up in my caller id was somewhat unwanted.

So I removed **1

Then I added 1xxxxxxxxxx|[2-9]xxxxxxxxx|#1XX.S3 to my AA digitmap

And I added {(Msp1):sp1},{(Msp3):sp3},{(Msp2):sp2} to my AA outbound call route.

So, this works just like dialing out as I normally would after I press "2" through the AA menu.
And initial callbacks are also routed as they normally would when dialing out from the ATA.

And I'm not getting **1 in my caller id.

Thank you

Navigation

[0] Message Index

[*] Previous page