" /> Busy Signal with OmniPCX and SIP T-Server - Genesys CTI User Forum

Author Topic: Busy Signal with OmniPCX and SIP T-Server  (Read 6478 times)

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Busy Signal with OmniPCX and SIP T-Server
« on: December 05, 2008, 03:31:17 AM »
Advertisement
Hi,

I was wondering if anyone knows of a way of how to return a busy signal to caller without being charged with OmniPCX+SIP T-Server+URS

Here is a scenario:

1. client is using 1-800 number
2. if person calls outside the regular working hours, they want to return busy.

The problem is obviously how to return busy without accepting the call. Is there some obviously simple way to do it? If we use Stream Manager to play "busy", call would be accepted and client would be charged.


Needless to say, the same problem would happen with any number, where person would call and even though they heard busy, they would be charged -- and that would cause a lot of problems.

With Avaya, we just forward the call to a non-existent VDN, causing POTS to detect an error and return busy to the caller without a charge.

Has anyone had to face this problem with OmniPCX?

Thanks,
Vic

Offline Dionysis

  • Sr. Member
  • ****
  • Posts: 408
  • Karma: 8
Re: Busy Signal with OmniPCX and SIP T-Server
« Reply #1 on: December 05, 2008, 07:33:12 AM »
The Alcatel should support "Cancel Call" using URS.

This will reject the call without answering it, what the network does with the call after that depends on the configuration in the network.

The SIP Server however, does not support this feature.


Offline Adam G.

  • Hero Member
  • *****
  • Posts: 552
  • Karma: 12
  • Still Gorgeous.......
Re: Busy Signal with OmniPCX and SIP T-Server
« Reply #2 on: December 05, 2008, 07:49:39 AM »
Why not close the line at the Network level - get your telco to do it? Here in the UK you can control the BT lines on the web and set open and close times, queue sizes etc.


Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Re: Busy Signal with OmniPCX and SIP T-Server
« Reply #3 on: December 05, 2008, 11:00:07 AM »
[quote author=Dionysis link=topic=3644.msg15498#msg15498 date=1228462392]
The Alcatel should support "Cancel Call" using URS.

This will reject the call without answering it, what the network does with the call after that depends on the configuration in the network.

The SIP Server however, does not support this feature.


[/quote]

Hi,

so, when you have OmniPCX<--->(SIP-TServer+URS), what can done? I assume RouteRequest from OmniPCX will still go to SIP-Tserver and URS, so something is still possible... After all, OmniPCX is just a VoIP gateway...

Regarding closing it on carrier level -- out of question, unfortunately. You right Pavel , that would be the fastest though...

How does everyone do it?

Offline jbobinsk

  • Jr. Member
  • **
  • Posts: 87
  • Karma: 1
Re: Busy Signal with OmniPCX and SIP T-Server
« Reply #4 on: December 05, 2008, 11:23:36 AM »
You can do this on Alcatel (since 7 version) - I don't know if it is possible on SIP Server. But on alcatel when caller is queued on RSI you can play anything (announcement, music, busy) and caller will not be charged - it is set in switch database by setting parameter taxfsda to (I don't remember if) 1 or 0 value. In such case Alcatel doesn't sent answer message to network. But there is a weak point of such configuration - in the network are timers which wait for answer message - if answer from PBX will not come in (usually) 100 sec then caller is released.

I hope this help

Regards
jbobinsk

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Busy Signal with OmniPCX and SIP T-Server
« Reply #5 on: December 05, 2008, 08:23:02 PM »
I think I have it.
In OXE...
When a call enters you can route it to an entity, a entity can have working hours, so if the entity is opened then will route the call to your SIP Gateway, if not route the call to a ghost extension (VirtualZ) and it will drop the call automatically as the entity of that GhostZ will be also disabling the option to go to the Operator.
I think it should work.

Offline Dionysis

  • Sr. Member
  • ****
  • Posts: 408
  • Karma: 8
Re: Busy Signal with OmniPCX and SIP T-Server
« Reply #6 on: December 05, 2008, 09:40:12 PM »
Cav, on an OXE you can use the cancel call treatment in router to do this.  No need to use the entity at all provided you don't play any message to the caller before sending the cancel call request.  There is some specific settings on the RSI to make this work though.

I've never worked with an OmniPCX, if it's just a gateway then I don't think using cancel call can work.

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Busy Signal with OmniPCX and SIP T-Server
« Reply #7 on: December 05, 2008, 09:52:16 PM »
The problem would be that if you route to an RSI then you have the call with an answered status and the caller will have to pay the call, for a local call no problem but imagine an international call...I know the cancel treatment, but again OXE must answer to do this.
OXE is much much much more than a Gateway as Vic says...