Page 1 of 1

Issues dialing into a satellite node

Posted: 03 May 2008 02:20
by Krusty65
Hi Guys, one word Heeeeeeelp!

I have an CLI issue with an OxO main/satallite configuration.

I am doing an satellite system @ a mine site in the middle of nowhere in outback Australia.

The main node has been in and working for some time and I am adding the second node with 30 IP Trunks between the two. Node 2 has no external accesses so is using the ISDN @ node 1.

The two sites have the same prefix to there external numbering 089213 with the last 4 digits being used in the public numbering plan, 4100 to 4199 is node 1, 3700-3899 is node 2

The set-up works node 1 can call node 2 and visa versa, node 2 can call the outside world

but

depending on the set-up in the ARS 1 of 2 things happens

if I have an entry in the public numbering plan of node 1 of

secondary tg/ 3700-3899 / ARS / NMT=keep / private=yes

and

an entry in the ARS prefixes of

activation=yes / network=private / prefix=37 / range=00-99 / substitute=37 / tg (VoIP tg) / called=hom

Then incoming calls are routed through to the user on node 2, but if I dial out from the user on node 2 the CLI presented to the outside world is 089213 and that is all.


However if I follow the guide both in the online help and the technical documentation and do

Public numbering plan

same as above

Ars prefixes

activation=yes / network=private / prefix=37 / range=00-99 / substitute=37 / tg (VoIP tg) / called=hom
activation=yes / network=private / prefix=08921337 / range 00-99 / substitute=37 / tg (VoIP tg) / called=hom

In this config the out going call still presents the wrong CLI but an incoming call routes to the operator on node 1



However after some messing around with the settings I have found


Public numbering plan

secondary tg 3700-3899 / ARS / NMT=keep / private=NO

Ars prefixes

activation=yes / network=private / prefix=37 / range=00-99 / substitute=37 / tg (VoIP tg) / called=hom
activation=yes / network=public / prefix=08921337 / range 00-99 / substitute=37 / tg (VoIP tg) / called=hom

In this config the out going call presents the correct CLI but an incoming call still routes to the operator on node 1

I have concentrated on the 37xx number range but 38xx is the same.




Other than this as I have said calls between the nodes are fine.

Re: Issues dialing into a satellite node

Posted: 03 May 2008 02:22
by Krusty65
Oops forgot to add that node 1 is R5.10 latest release and node 2 is R6.10 latest release

Re: Issues dialing into a satellite node

Posted: 04 May 2008 05:36
by Krusty65
Ok so after two days messing with settings and reading/re-reading the manual I discovered the deliberate mistake :evil: in the documentation.

Strangely enough the technical docs has one half of the set-up right and the online help in OMC has the other half of it right by combining the two in just the right way with a pinch of red dust and a large amount of swearing I came up with the correct combination.

So no worries on this one.

Re: Issues dialing into a satellite node

Posted: 05 May 2008 02:39
by Jigger
is the mine griffin group?

Re: Issues dialing into a satellite node

Posted: 05 May 2008 03:18
by Krusty65
Naaa that's OxE :)

This one is really in the middle of nowhere 900kms N/W of Alice