TRUNK SECURiTY , TAIL END HOPS >>>MULTITECH VOIP<PRI>

[DblDown]

I'm have some routing problems between voip gateways when trying to TAIL end Hop.
The situation is this, office(A) calls an assigned 4 digit EXT (ARS) to OFFICE(B) (VIA)->Rout pattern->(ISDN TIE) TRUNK GROUP->VOIPGATEWAY(A) ---Dedicated bandwidth-- to ->VOIPGATEWAY(B)->PrologicTRUNK GROUP(b)-> VDN(assigned ext)-> VECTOR ROUTE (OFFSITE Number). actually at the end here is a fast busy. but should be (offsite number). THE CORs and FRLs through the process are constant but over the voip trunk groups is not letting me (offsite). NOW if I dial the same assigned EXT VIA PSTN trunk group From office(a) to office(B) Hit the same VDN/VEC (OFFSITE) the call will connect properly. So I think its some security "feature" or something keeping me from coming in VOIP TRUNK AND BACK OUT PSTN TRUNK. any one have any Idea what I can check (security wise) to find out why the PBX wont let this call out, but will let a PSTN call connect?

So to recap.

dialing a VDN EXT FROM SITEA Via a working VOIP GATEWAY CONFIGURATION to siteb (fast busy) and Im sure the call is getting all the way to the vector on siteb but the PBX is blocking.

Dialing the same VDN Via PSTN from siteA to siteB allows call to connect.

any help will be appreciated.



Equipment

SiteA G3si V7 ISDNPRI TG CONNECTED TO MULTIVOICE 2410

 

[BuckWeet]

Sounds like a FRL, COR, or improper digit passing to me..

Have you done like a 'list trace tac' on the trunk groups to see why its rejecting it??

'list trace tac' is your ultimate friend..


BuckWeet

 

[DblDown]

What VER# or ADMIN RIGHTS do you need for this command ?

This PBX is VER 7.xx..

 

[BuckWeet]

The command might not be in release 7, i'm not sure when they added it, i know R6 doesn't have it, but I've not worked much on R8's or R7's...


BuckWeet

 

[DblDown]

ANYWAY AFTER GOING THROUGH JUST ABOUT EVERTHING I COULD THINK OF IT ENDED UP BEING "DISCONNCET SUPERVISTION IN = Y" IN THE VOIP TRUNKGROUP.. THANKS FOR THE HELP ANYWAY. Here is the expalnation "if you care" , MY VOIP TRUNKS HAD NO SUPERISION. DAMN KIDS Thanks again.

Disconnect Supervision
Disconnect supervision means the CO has the ability to release a trunk when the
party at the CO disconnects, and the system is able to recognize the release
signal. In general, a CO in the United States provides disconnect supervision for
incoming calls but not for outgoing calls. Many other countries do not provide
disconnect supervision on either incoming or outgoing calls.
The system must provide the assurance that at least one party on the call can
control the dropping of the call. This avoids locking up circuits on a call where no
party is able to send a disconnect signal to the system. Internal operations must
check to be sure one party can provide disconnect supervision. An incoming
trunk that does not provide disconnect supervision is not allowed to terminate to
an outgoing trunk that does not provide disconnect supervision.
In a DCS environment, an incoming trunk without disconnect supervision can
terminate to an outgoing DCS trunk connecting two nodes. The incoming trunk is
restricted from being transferred to a party without disconnect supervision on the
terminating node.