Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Closing a call started from Pbx extension using 3pcc

  1. #1

    Default Closing a call started from Pbx extension using 3pcc

    We want to be able to restrict outgoing calls based on configuration and called number. Is this possible using the 3pcc?

    From a DialogArrived event, closing the call on a callID (CloseCall()) returns true but has no effect and the call continues regardless.

  2. #2

    Default Closing a call started from Pbx extension using 3pcc

    Hello.

    You can close calls which are created with CreateCall or handled by OnCallArrived event.
    You can restrict outgoing calls by using routing rules with 3pCC check. Your 3pCC application should decline call indicated by OnCallOriginated event to restrict it.

    Hope this will help.

    Regards
    Tigran
    Last edited by intigran; 08-10-2009 at 02:07 PM.

  3. #3

    Default

    Quote Originally Posted by intigran View Post

    You can restrict outgoing calls by using routing rules with 3pCC check. Your 3pCC application should decline call indicated by OnCallOriginated event to restrict it.
    Hi Tigran,

    Thanks for this. I do not seem to have OnCallOriginated in any of my documentation or withing the control itself. I am running Quadro control 2.0.3.0.

    Is there an alternate version with more functionality?

  4. #4

    Default

    Hello.

    What is your Quadro's firmware version?

    Thanks
    Tigran

  5. #5

    Default

    Quote Originally Posted by intigran View Post
    Hello.

    What is your Quadro's firmware version?

    Thanks
    Tigran
    Firmware Version: 5.0.16SLR/Release

  6. #6

    Default

    hi,

    If it is possible please upgrade your firmware to 5.1.x,
    For SW 5.0.x use ActiveX 2.0.5.0 version, SW 5.1.x use ActiveX 2.1.2.0 version, which are placed on Downloads section at http://www.epygi.com.

    Thanks
    Tigran

  7. #7

    Default

    Quote Originally Posted by intigran View Post
    hi,

    If it is possible please upgrade your firmware to 5.1.x,
    For SW 5.0.x use ActiveX 2.0.5.0 version, SW 5.1.x use ActiveX 2.1.2.0 version, which are placed on Downloads section at http://www.epygi.com.

    Thanks
    Tigran
    Hi Tigran,

    I have done this at last.

    I am now subscribing to the call routing (SubscribeToCR method) which is returning ok in a SubscriptionConfirmed event.

    Problem is tha the CallOriginated event never fires. I have ensured that 3PCC is enabled in the relevant routing table lines.

    Any ideas as to why this event does not fire?

    Thanks

  8. #8

    Default

    Hi.

    Please clarify what is your installed ActiveX version. Did you try to catch that event with CallControlTest application included in CallControl Pack?

    Thanks
    Tigran

  9. #9

    Default

    Quote Originally Posted by intigran View Post
    Hi.

    Please clarify what is your installed ActiveX version. Did you try to catch that event with CallControlTest application included in CallControl Pack?

    Thanks
    Tigran
    Hi Tigran,

    ActiveX conrtrol is 2.1.2.0

    I have run the CallControlTest application and it works fine.

    However, I am coding in vb.net (2008)

    All the events fire correctly except for the CallOriginated event.

    I have stripped down the code to a test version as shown below which still fails:

    Public Class Form1

    Private m_strCrSubscriptionId As String = ""

    Private m_blnIsConnected As Boolean = False

    Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
    m_blnIsConnected = AxCallcontrol1.Connect("xxx.xxx.xxx.xxx", 4849, 10, "admin", "xxxxxx")

    lblOK.Visible = m_blnIsConnected
    End Sub

    Private Sub btnRegister_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles btnRegister.Click
    m_strCrSubscriptionId = AxCallcontrol1.SubscribeToCR
    End Sub

    Private Sub AxCallcontrol1_CallOriginated(ByVal sender As Object, ByVal e As AxCALLCONTROLLib._DCallcontrolEvents_CallOriginate dEvent) Handles AxCallcontrol1.CallOriginated
    MsgBox("Originated")
    End Sub

    Private Sub AxCallcontrol1_SubscriptionConfirmed(ByVal sender As Object, ByVal e As AxCALLCONTROLLib._DCallcontrolEvents_SubscriptionC onfirmedEvent) Handles AxCallcontrol1.SubscriptionConfirmed
    If e.subscrID = m_strCrSubscriptionId Then
    btnRegister.BackColor = Color.Green
    End If
    End Sub
    End Class

  10. #10

    Default

    Hi.

    We found that there is problem in CallOriginated event while using vb.net 2008. The problem fixed and it will be included in the next release. The next release is expected to be published in the second half of next month.
    If you need that very urgently I can e-mail it to you.

    Thanks,
    Tigran

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Ability to sort by extension in User Extension management
    By woods in forum Suggestions and Feedback
    Replies: 4
    Last Post: 08-03-2009, 09:16 PM
  2. Transfer call to virtual extension
    By tpeixinho@netdominium.pt in forum Troubleshooting and Problems
    Replies: 7
    Last Post: 07-13-2009, 01:36 PM
  3. inbound call extension timeout - 3minutes max?
    By edgarlopes in forum Troubleshooting and Problems
    Replies: 2
    Last Post: 05-04-2009, 04:46 PM
  4. 3pcc c++
    By progisoft in forum 3PCC
    Replies: 1
    Last Post: 01-21-2009, 11:42 AM
  5. FX0 call not closing
    By TFIDemo in forum Troubleshooting and Problems
    Replies: 3
    Last Post: 01-22-2008, 10:29 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •