Remote Trunk Access

[bmwfw22]

I need to allow remote employees to be able to access a particular trunk. Internal employees simply dial 305 and automatically get in and obtain a second dial tone from our VoIP system. To give access to our remote employees, I have programmed a VDN that points to a vector which in turns dial the TAC (305). Unfortunately the PBX automatically adds a # sign at the end to signify the end of the dial string.

Is there another way to prevent the PBX from adding the # sign or doing this differently?

Thanks

 

[dufus2506]

On the second page of the trunk group definition try setting "suppress # outpulsing" to Y.

Carpe dialem! (Seize the line!)

 

[bmwfw22]

That suppressed the # sign which is good. Now the PBX sends 0. Any reason why this would be?

 

[bmwfw22]

i guess it does not. Thanks

 

[bmwfw22]

Are there any other means of accessing a Trunk group from outside the PBX?

 

[multibus2]

If the trunk is ISDN and it's digit handling is set to enbloc it is expecting a complete digit string like it would get when a call is routed via ars. If it set to overlap it will send one digit at a time rather than a block of digits.
Now some CO's will except either however if it is set to enbloc only the first digit is sent the in D channel call set-up message, any other digits are sent in-band, ie over a B channel as DTMF when the TAC is used rather than ars routing. I don't belive that the Definity records the in-band DTMF. This possibly why you just see one digit only (0) as it most likely your first digit dialed. If the call is not routed via the CO then they may not except overlap or in-band dialing.

 

[bmwfw22]

We do not have ISDN, but have found a work around for this issue. I have turned on remote access and restricted access to a specific TAC with a custom COR. Thanks