AA option to ring extension on remote OXO via SIP link

[pateldiv84]

Hi Guys.

Thanks all for your suggestions.

ET - Yes, I had a look at your advice and allowed all the joining and external transfer under features for all voicemail terminals, and amazingly its started working! Yes, its was a feature issue but more on the voicemail side rather then the users/hunt group end. Thanks for your help on this.

Also, not sure if you guys read the second issue or not. We also need to use free dialing to allow external calls to dial extensions on the remote switch. Free dialing local station works fine, however when we try free dialing the remote extension (anything in 300 range) the AA prompts this as an invalid entry?

Can remote extensions be dialed using free dialing or am I chasing shadows? :-p

Cheers!

[et]

Try to use remote destination in Internal numbering Plan, first for one remote extension, because I am not sure this working or Not. Function= remote destination; start=301; end=301; Base= base of trunk group, used to reach second OXO (in your case - SIP trunk group). And NOT an EDN of the trunk group: Main trunk Group has Base=0, Secondary - from 1 to 119. If this working, try to replace start/end=3. If not - than another solution, but with disadvatages. How much remote extensions you have, and how much local subscribers?

[pateldiv84]

Hi et.

Thanks for your reply.

I tried entering the number plan you suggested. Funct: Remote Destination, Start:399, End:399, Base:1 (this is because my secondary TG are 82->88 and the voip trunks sit under TG 82).

The moment I enter the free dialling option and dial 399, the AA presents annoucement "You will be transfered to Ext 0". The call doesn't actually hit ext 399, instead it starts ringing in the Attendant group on Oxo1.

Any suggestions or ideas why it would do this? Since I'm only pointing to the TG that has the SIP trunks, how would the call know what IP address the call needs to go to, as this would be done in the ARS table which the call will never hit?

[selectt_DUP]

Still no joy, basically if the number does not exist on the main reference site the call will not route via the free dialing option to the the remote site. To combat this i created some speed dial numbers with the prefix * ie *300-*399, the remote extns being 300-399. But if a call is routed via the AA free dialing the * option on the AA kicks in and basically routes back to itself, if i could disable the * feature on the AA ,the customer could live with the * prefix for incoming AA/free dialing , any ideas other than giving the customer two extn numnbers one for AA and one local ?

[pateldiv84]

Thanks for your post Selett.

I have been working along the same trail. How I've got it working is using the normal speed dial series 7000. As all my remote users are in the range 300-399 and I've got speed dials running from 7000-7399. I've basically used everything from 7300-7399 and pointed these to the remote extensions.

So now the remote users just advertise their extensions as 73XX instead of 3XX. This seems to be working fine for me and the customer seems to be happy with it as well.

Cheers!

[et]

You can add one more Collective speed dial range in Internal Numbering Plan of main OXO: Function: Collective speed dial; Start=300; End=399; Base=300.

[et]

You can replace prefix in Internal Numbering Plan for the secondary Tunk Group to go to ARS for remote OXO users from "3" to "A3". And modify entry in ARS: Prefix=A3; Substitute=3. In speed Dial you need to go to "A3".