Setting Inbound And Outbound Ports

[Guest miva]

Hi,

 

I am using VG7 for a conference and record application. I have set the script to allow dial out on lines 6,7,8,9 and 10 only. As calls come in, they immediately set up the outbound call. So in effect Line 1 will dial out on Line 6 and Line 2 on Line 7 and so on.

 

There has been the odd occassion when all 5 incoming lines are busy (possibly still running part of the script) and one of the outgoing lines (say Line 6) has cleared down. This means (in the current setup) that Line6 will take the next call but will not be able to dial out as all outgoing lines are busy.

 

What I want to be able to do is set Lines 1 to 5 as incoming only and Lines 6 to 10 as outgoing only. How can I do this?

 

The simple solution would be to buy more licences and increase our line capacity which we are in the process of doing but still want an interim solution. Once the ISDN is increased we will be after a further 4 licences at the least.

[SupportTeam]

The outgoing line selection can be set using the Config.xml file or by specifying the allowed channels at each individual call load time. Looks like the system is using these methods to select the outgoing channels already.

 

If you are unable to configure the remote system to prevent it from sending calls on channels 6-10 then the only possible action to stop incoming calls being answered on these channels would be to disconnect any calls which arrive on these channels. The way to do this is to create a script which "Starts without answering the call" and just consists of a single hangup module. Then assign that script to channels 6-10. This way calls arriving on channels 6-10 should get disconnected without ever being answered. This would of course result in dropped calls and the caller getting a "Disconnected" signal...

 

[Guest miva]

The suggestion of hanging up on the caller is not really a suitable option. Can you confirm that the call will not be answered and that VG will present a busy tone as opposed to a "disconnected" tone (not sure if there is a difference). If a busy tone was presented to the call, I would expect that any overflow conditions set on the line they called would come into effect and this may be suitable.

 

I assume that if there was a better way then you would have suggested it, but I will ask anyway. Is there a better way?

[SupportTeam]

It is possible to specify an ISDN "Disconnection Cause" when the call is being disconnected. The disconnect causes which can be sent over ISDN lines are:

 

CALL_REJECTED

CHANNEL_UNACCEPTABLE

DEST_OUT_OF_ORDER

NETWORK_CONGESTION

NORMAL_CLEARING

REQ_CHANNEL_NOT_AVAILABLE

SEND_SIT

UNASSIGNED_NUMBER

USER_BUSY

 

Right now VoiceGuide sends the NORMAL_CLEARING disconnection cause. Which is appropriate to send when hanging up a call that has been answered.

 

As in this case you would like to disconnect/reject a call without answering it, then sending of other disconnect causes may be useful in this situation. The systems sending the call may be able to read the disconnect cause value and react appropriately.

 

Please contact sales@voiceguide.com for a quote on having the software modified to be able to send a user-specified disconnect cause.

[ktruk]

support: The ability to 'busy-out' inbound lines would be great. Good for systems being offline, for instance. Is it a big job to add a cause-code to the vg.ini or similar? Thx.

[SupportTeam]

On ISDN lines the ISDN link is effectively 'busied out' when the VoiceGuide service is stopped. All the channels are marked as "closed" by the Dialogic card/drivers and no calls are then accepted on those channels. Not sure what cause code the Dialogic card sends under those conditions. This may be selectable on the Dialogic driver level.