Jump to content

Search the Community

Showing results for tags 'CSTA'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • App Topics
    • Android App
    • iOS App
    • Windows App
    • MacOS App
  • News
    • Announcements
    • New Features/Versions
    • Product/Site Comments
    • Polls
  • Using the PBX
    • Using Cell Phones
    • Web Interface
    • Call Treatment
    • Call Recording
    • Security
  • Marketing Exchange
    • Customer Research
  • Product Setup
    • General Setup
    • Best Practices
    • PAC and WAC
    • Trunk Setup
    • Dial Plan Setup
    • Extension Setup
    • Mailbox
    • Conference Room Setup
    • Auto Attendant Setup
    • IVR Node Setup
    • Agent Group Setup
    • Hunt Group Setup
    • Calling Card Setup
    • Paging Setup
    • Service Flags
    • Music on Hold
    • SOAP
    • SNMP
    • Embedded
    • Linux-related Topics
    • Windows-related Topics
    • MacOS related topics
    • FreeBSD-related topics
    • CDR
    • snomONE Plus
    • Virtual Appliances
  • Connectivity To Other Services and Components
    • Gateways
    • ITSP's
    • VoIP Phones
    • Microsoft Interoperability
    • Integrations
    • SMS Inbound / Outbound Settings
    • Email Topics
    • Fax Setup
    • Firewalls and NAT
    • Hosting
  • Non-English
    • French
    • German
    • Spanish
  • Business Topics
    • Service Providers that support the Vodia PBX
    • Integrators
  • Other
    • PBX Lounge
    • Question About The Forum
  • Partner Area
    • General Topics

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. socnet

    CSTA - group calls

    Using CSTA on a v5.1 Snom One in a hosted environment. When an incoming call rings several devices, there appears no way to associate the multiple legs of the call. The "call ids" are different, for instance. Is there any way to get data that would allow us to know that these are the same call? Thanks
  2. Using CSTA on a v5.1 Snom One in a hosted environment. When we receive a simple incoming call to a group of extensions, then information is correct (some information is obscured with xx): IN: <DeliveredEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed4"><monitorCrossRefID>413</monitorCrossRefID><connection><callID>37ee52d1@pbx</callID><deviceID>2653@domain</deviceID></connection><alertingDevice><deviceIdentifier>6129xxxxxxx@175.x.x.x</deviceIdentifier></alertingDevice><callingDevice><deviceIdentifier>6141xxxxxxx@domain</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>6129xxxxxxx@175.x.x.x</deviceIdentifier></calledDevice><lastRedirectionDevice><notKnown /></lastRedirectionDevice><localConnectionInfo>alerting</localConnectionInfo><cause>normal</cause><IORef xmlns="">9999</IORef></DeliveredEvent> However, when we answer the call (by lifting the handset) then the "caller" and "called" switch, which is wrong. IN: <EstablishedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed4"><monitorCrossRefID>413</monitorCrossRefID><establishedConnection><callID>37ee52d1@pbx</callID><deviceID>2653@domain</deviceID></establishedConnection><answeringDevice><deviceIdentifier>6141xxxxxxx@domain</deviceIdentifier></answeringDevice><callingDevice><deviceIdentifier>6129xxxxxxx@175.x.x.x</deviceIdentifier></callingDevice><calledDevice><deviceIdentifier>6141xxxxxxx@domain</deviceIdentifier></calledDevice><lastRedirectionDevice><notKnown /></lastRedirectionDevice><localConnectionInfo>connected</localConnectionInfo><cause>normal</cause><IORef xmlns="">9999</IORef></EstablishedEvent> This only appears to happen for incoming calls, not outgoing. Hopefully the text above is obivous enough, but I can provide more information if needed.
  3. Using CSTA on a v5.1 Snom One in a hosted environment. When we are using CSTA to do consultation calls we receive a corrupt XML response to the request. The request is: 0032<?xml version='1.0' encoding='UTF-8' standalone='yes'?><ConsultationCall><existingCall><callID>4cdff04b@pbx</callID><deviceID>2654@domain</deviceID></existingCall><consultedDevice>2653</consultedDevice></ConsultationCall> The response is: 0032<?xml version="1.0" encoding="UTF-8"?><ConsultationCallResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed4"><initiatedCall><callID>52d470a7@pbx</callID><deviceID>2654@domain</deviceID></</initiatedCall>></ConsultationCallResponse> Hopefully the fault is obvious (around "/initiatedCall"). The problem happens consistently. Looks like a straightforward fault. Thanks in advance
  4. Using CSTA on a v5.1 Snom One in a hosted environment. When we transfer incoming calls (using our handsets) then the original caller's telephone number is not provided in any of the CSTA messages to the new extension. Nor is there any correlating information that allows us to link the new call to the original received call. This is unexpected. Is there a way that we can receive either the original caller information or calculate a link? We tried SnapshotDevice but there was nothing interesting in the response. thanks
×
×
  • Create New...