Can anyone tell me what settings will work to get a test phone registering?

Hello,

I'm sure this is an easy one, but I'm just starting on CTI and am trying to figure out the basics.

I am sending the below CTI message

<?xml version="1.0" encoding="UTF-8"?><xsp:request xmlns:xsp="http://schema.broadsoft.com/XspXMLInterface" version="17.0"><requestId>2</requestId><sessionId>635197977378722922</sessionId><credentials>NDQyMDgyODgxMjQ4QGRyZC5jby51azpwYXNzd29yZDCyMw==</credentials><xsp:payload><cti:AddUserSubscriptionRequest xmlns:cti="http://schema.broadsoft.com/CTI"><cti:uri>/com.broadsoft.xsi-events/v2.0/user/%userId%</cti:uri><cti:method>POST</cti:method><cti:version>17.0</cti:version><cti:params><userId>TestUser@drd.co.uk</userId></cti:params><cti:payload><Subscription xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><xsi:event>Basic Call</xsi:event><xsi:expires>3600</xsi:expires><xsi:channelSetId>ChannelSet79773</xsi:channelSetId><xsi:applicationId>TestClient123</xsi:applicationId></Subscription></cti:payload></cti:AddUserSubscriptionRequest></xsp:payload></xsp:request>

But the server is returning the below

<?xml version="1.0" encoding="UTF-8"?><xsp:response xmlns:xsp="http://schema.broadsoft.com/XspXMLInterface" version="17.0"><requestId>2</requestId><sessionId>192</sessionId><statusCode>409</statusCode><reason>Conflict</reason><xsp:payload>
<ErrorInfo xmlns="http://schema.broadsoft.com/xsi"><summaryEnglish>Invalid Xml</summaryEnglish><errorCode>1116</errorCode></ErrorInfo></xsp:payload></xsp:response>

What am I doing wrong?  Any help is appreciated, maybe with a sample of what I'm supposed to send?

Also, is there a way to see the CTI messaging in log files on the Broadworks server? If so can you please confirm how to enable it on the server and where to find the log files? I've looked in /bw/broadworks/logs/xsp but can't see them.

Thanks

I am getting 409 Conflict -- "missing entity body in request" error on submitting a heartbeat request to my providers site (can't replicate on sandbox at this time b/c sandbox returns an error on the subscription call, per my post earlier today)

Here is the fiddler trace for the request/response.  Can you provide a trace of a successful heartbeat transaction so that i can see what should be sent in the body?

 Heartbeat request

PUT http://xsp.metconnect.com/com.broadsoft.xsi-events/v2.0/channel//heartbe... HTTP/1.1

User-Agent: App Client

Content-Type: application/xml;charset=UTF-BOM

Authorization: Basic bmVzYXBpMUBhc255Yy5tZXRjb25uZWN0LmNvbTpYZXZlbnRzbmVzMg==

Host: xsp.metconnect.com

Content-Length: 0

Heartbeat Response

HTTP/1.1 409 Conflict

Date: Mon, 11 Nov 2013 21:32:53 GMT

Server: BW HTTP Server

Set-Cookie: JSESSIONID=C307CDCBE8FE5EE829C086B990A373FB; Path=/com.broadsoft.xsi-events

Expires: Thu, 01 Jan 1970 00:00:00 GMT

Content-Language: en-US

Cache-Control: no-store

Pragma: no-cache

Content-Length: 192

Content-Type: application/xml;charset=UTF-8

<?xml version="1.0" encoding="UTF-8"?>

<ErrorInfo xmlns="http://schema.broadsoft.com/xsi"><summaryEnglish>Missing entity body in request</summaryEnglish><errorCode>1102</errorCode></ErrorInfo>

I am getting error 403 Forbidden, channelsetid not found on my subscription request.  Subscription request is going out immediately after channel response is received.

Here is the fiddler trace fro the commands:

Channel Request

POST http://xsp1.xdp.broadsoft.com/com.broadsoft.async/com.broadsoft.xsi-events/v2.0/channel HTTP/1.1
Authorization: Basic YW5lbHNvbl9uZXNyZW50YWxzVXNlcjFAeGRwLmJyb2Fkc29mdC5jb206d2VsY29tZTE=
Host: xsp1.xdp.broadsoft.com
Content-Length: 209
Expect: 100-continue

<?xml version="1.0" encoding="UTF-8"?><Channel xmlns="http://schema.broadsoft.com/xsi"><channelSetId>NESCh11122013100156</channelSetId><priority>1</priority><weight>50</weight><expires>3600</expires></Channel>

Channel Response

HTTP/1.1 200 OK
Date: Tue, 12 Nov 2013 15:00:56 GMT
Server: Apache-Coyote/1.1
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Language: en-US
Cache-Control: no-store
Pragma: no-cache
Content-Type: application/xml;charset=UTF-8
Set-Cookie: JSESSIONID=DCC3A000D47F6D00CEDE8EE62CFF03C2; Path=/com.broadsoft.xsi-events
Transfer-Encoding: chunked

b4
<?xml version="1.0" encoding="UTF-8"?>
<Channel xmlns="http://schema.broadsoft.com/xsi"><channelId>53897fb3-6835-4728-a853-b5ef8d427693</channelId><expires>3600</expires></Channel>
0

Subscription Request

POST http://xsp1.xdp.broadsoft.com/com.broadsoft.xsi-events/v2.0/user/anelson_nesrentalsUser1@xdp.broadsoft.com/subscription HTTP/1.1
User-Agent: App Client
Authorization: Basic YW5lbHNvbl9uZXNyZW50YWxzVXNlcjFAeGRwLmJyb2Fkc29mdC5jb206d2VsY29tZTE=
Host: xsp1.xdp.broadsoft.com
Content-Length: 286
Expect: 100-continue

<?xml version="1.0" encoding="UTF-8"?><Subscription xmlns="http://schema.broadsoft.com/xsi"><targetIdType>User</targetIdType><event>Basic Call</event><expires>3600</expires><channelSetId>NESCh11122013100156</channelSetId><applicationId>NESCh11122013100156</applicationId></Subscription>

Subscription Response

HTTP/1.1 403 Forbidden
Date: Tue, 12 Nov 2013 15:01:28 GMT
Server: BW HTTP Server
Set-Cookie: JSESSIONID=8E16B7B96A882642175CB70E6C69319F; Path=/com.broadsoft.xsi-events
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Language: en-US
Cache-Control: no-store
Pragma: no-cache
Transfer-Encoding: chunked
Content-Type: application/xml;charset=UTF-8

109
<?xml version="1.0" encoding="UTF-8"?>
<ErrorInfo xmlns="http://schema.broadsoft.com/xsi"><summary>Channel set NESCh11122013100156 not found</summary><summaryEnglish>Channel set NESCh11122013100156 not found</summaryEnglish><errorCode>110842</errorCode></ErrorInfo>
0

Hi,
Can you please tell if it is possible to Monitor a Line which is on DND.
If so how can it be acheived and please provide a detailed information for the solution ASAP.
Our BW-Platform:19.0

I got a reply from Joëll in Exchange Forum and here is the reply:
You should use CAP in combination with the command 'monitoringUserRequest' to achieve this.

But from the above Reply I did not get detailed info. If any one can help me out on this, would be great.

Thanks in advance.

We want to be able to retrieve voicemail message from Broadsoft Voicemail service and get the audio file of the message. Is that possible and how? Thanks.

When I submit a channel request, and receive a successful response, then try to submit a subscription request using the same channelsetID, it it returning a channel not found error?  Can you explain what it happening?  Submitting the same commands to my providers site (metconnect) actually returns a valid subscription response.

Channel Request:

POST http://xsp1.xdp.broadsoft.com/com.broadsoft.async/com.broadsoft.xsi-events/v2.0/channel HTTP/1.1
Authorization: Basic YW5lbHNvbl9uZXNyZW50YWxzVXNlcjFAeGRwLmJyb2Fkc29mdC5jb206d2VsY29tZTE=
Host: xsp1.xdp.broadsoft.com
Content-Length: 209
Expect: 100-continue

<?xml version="1.0" encoding="UTF-8"?><Channel xmlns="http://schema.broadsoft.com/xsi"><channelSetId>NESCh11112013103251</channelSetId><priority>1</priority><weight>50</weight><expires>3600</expires></Channel>

Channel Response

HTTP/1.1 200 OK
Date: Mon, 11 Nov 2013 15:31:54 GMT
Server: Apache-Coyote/1.1
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Language: en-US
Cache-Control: no-store
Pragma: no-cache
Content-Type: application/xml;charset=UTF-8
Set-Cookie: JSESSIONID=E05441E6D1A7E230573EB2BF8556CE16; Path=/com.broadsoft.xsi-events
Transfer-Encoding: chunked

b4
<?xml version="1.0" encoding="UTF-8"?>
<Channel xmlns="http://schema.broadsoft.com/xsi"><channelId>9e5ce3ce-b503-449d-a27c-a6de233770d2</channelId><expires>3600</expires></Channel>
0

Subscription Request

POST http://xsp1.xdp.broadsoft.com/com.broadsoft.xsi-events/v2.0/user/anelson_nesrentalsUser1@xdp.broadsoft.com/subscription HTTP/1.1
User-Agent: App Client
Authorization: Basic YW5lbHNvbl9uZXNyZW50YWxzVXNlcjFAeGRwLmJyb2Fkc29mdC5jb206d2VsY29tZTE=
Host: xsp1.xdp.broadsoft.com
Content-Length: 286
Expect: 100-continue

<?xml version="1.0" encoding="UTF-8"?><Subscription xmlns="http://schema.broadsoft.com/xsi"><targetIdType>User</targetIdType><event>Basic Call</event><expires>3600</expires><channelSetId>NESCh11112013103251</channelSetId><applicationId>NESCh11112013103251</applicationId></Subscription>

Subscription Response

HTTP/1.1 403 Forbidden
Date: Mon, 11 Nov 2013 15:32:25 GMT
Server: BW HTTP Server
Set-Cookie: JSESSIONID=8FF6FCF835D1D4335F843DD32235D38D; Path=/com.broadsoft.xsi-events
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Language: en-US
Cache-Control: no-store
Pragma: no-cache
Transfer-Encoding: chunked
Content-Type: application/xml;charset=UTF-8

109
<?xml version="1.0" encoding="UTF-8"?>
<ErrorInfo xmlns="http://schema.broadsoft.com/xsi"><summary>Channel set NESCh11112013103251 not found</summary><summaryEnglish>Channel set NESCh11112013103251 not found</summaryEnglish><errorCode>110842</errorCode></ErrorInfo>
0

Can someone please provide me information on how to get the call center monitoring suibscription to work?  I am trying to find the best way to monitor all call centers and I keep getting a 403 error when subscribing via user subscription.   If I am a supervisor and monitor queues within broadsoft, what is the best method?

Dear Team,

Please accept the following defect report.

Newest XSP Server Patches Restrictively Apply Overload Controls

When certain new XSP server patches are applied to the XSP Server, the Overload Control logic is immediately affected and made far too restrictive for normal CTI Interface API application usage, where even submitting 5 concurrent requests causes the XSP server to never ever respond to inbound requests.

Specifically on several Providers, the following Release 17 patch causes this to occur, but we also suspect there might be other patches that do this similarly for other BroadWork platform releases:

AP.platform.17.sp4.197.ap194291
AP.platform.17.sp4.197.ap201782

To undo these restrictions applied by the latest patch, the Provider has to remove all Overload Control settings for XSI-Actions and then re-apply them as follows in order to get the same behaviour before the patch was applied:

XSP_CLI/Applications/Xsi-Actions_8.6.12/OverloadControls>
userServiceTransactionLimit=100
restrictUserServiceTransactions=false
globalServiceTransactionLimit=10000
restrictGlobalServiceTransactions=true
globalCallsTransactionLimit=100
restrictGlobalServiceTransactions=true
restrictUserProfileTransactions=false

XSP_CLI/System/CommunicationUtility/DefaultSettings> get
reconnectionTimerSecs=300
responseTimeoutSecs=30
globalTransactionLimit=65535
userTransactionLimit=65535
transactionLimitPeriodSecs=5
useSecureBCCT=false
honorTrustsForBasicAuth=true

We recommend this defect should have 3 simultaneous resolutions:

1. Notify BroadSoft Support
The BroadSoft support team do not appear to have a great deal of internal knowledge on the CTI Interface API and what settings might adversely affect its operation.
We therefore recommend that the support team(s) should be made aware which BroadWorks XSP server patches have actually changed the Overload Control behaviour, and how that might affect external applications. 

2. Make Subsequent Patches Less Restrictive
We would recommend that subsequent patches undo some of the default over-restrictions applied to the CTI Interface, as for the CTI Interface API connections supporting several large Enterprises, it is very feasible for a CTI application to be submitting over 50 concurrent call control requests due to simultaneous Customer application call control invokations.

3. Ensure Patch Release Notes Are Updated Accordingly
The "Disposition" heading in the release notes associated with patches should clearly state how the XSP Overload Control behaviour is going to be affected by the patch after it is applied.

Regarding the following: 

XSI Interface Specifications PDF, on page 296, in chapter 4.7.7 C

allCenterMonitoringEvent states:

An event is generated when:

* An agent is assigned or unassigned from the call center

* An agent’s staffed status changes

* A staffe  agent’s idle status changes

* A staffed agent transitions to or from the Unavailable state

* An ACD call is added to the queue

* An ACD call is removed from the queue

* Following an initial subscription or refresh

But, when we do assign/unassign agent from callcenter -> event just doesn't come. so, is that some kind of bug?

First time we tried against sandbox we actually got 1 event. But then it stopped sending events for these changes.

What can be wrong? 

We have a web-app that subscribes for Basic Call events and displays when agents are either Signed out, Available, Unavailable or "On-Call'. Previously the On-call status was determined by directly querying the agent after receiving a call event and counting to see if the number of active calls was greater than zero.

In the interest of reducing traffic and pressure on the system, we've attempted to aquire all information strictly from the information in the received subscription events for agents (Basic Call and Call Center Agent). The only part that is unclear, is how to interpret the basic call events to determine whether an agent is "on-call" or not. The event name and/or call state in the event payload does not always seem to correlate with the on-call status displayed in the telesphere web client, or our previous version of software.

Is there a consistent way to determine whether the agent is "On-Call" strictly from subscription events, either from the basic call package, or other event packages? 

Thank you

Hello,

 I finally get it done to forward a call with the Xsi interface. The following step is to get the information about the a exention.

To get registration info i use this url <server>/com.broadsoft.xsi-actions/v2.0/user/<user>/profile/registrations. The first time the browser asks my credentials, and the url is typed directly in my browser.

 My goal is to do this from my own portal. So i can desgin the XML structure with css, and the direct url is not visible for my customers. The username and password of the user is stored in a database, and i am programming in PHP

 Hopefully someone could help me. 

I am getting an invalid XML response when submitting the even below.  Just upgraded to 19.1 this does work on 17.x  Let me know if this event has been deprecated.

http://xsp.com/com.broadsoft.xsi-events/v2.0/user/1232224444@xsp.coom
<?xml version='1.0' encoding='UTF-8'?>
<Subscription xmlns='http://schema.broadsoft.com/xsi'>
    <event>Call Center Monitoring</event>
    <expires>1</expires>
    <httpContact>
        <uri>111.111.111.111callcenter/subscription/index</uri>
    </httpContact>
    <applicationId>test</applicationId>
</Subscription>

<?xml version="1.0" encoding="UTF-8"?><xcap-error
xmlns="urn:ietf:params:xml:ns:xcap-error"><schema-validation-error
phrase="Invalid Xml"> </schema-validation-error>
</xcap-error>
 

The link on the Sandbox Documentation page for Using SIP-based clients/devices (http://developer.broadsoft.com/sandbox/documents/usingWithSIP) is broken.  It just opens to a page that says Page not found.

Does anyone have the correct URL? 

Hi,

My name is Icaro and I am a senior developer at TVD New Zealand, for the past few weeks we have been trying to create a integration between our software Avalanche and BroadSoft platform.

So far the maximum we could archive was manually create our basic setup using your website and establish a soap connection and execute few basic commands. Anyhow your main goal is to update new greeting messages.

To do so we are using the XML schema GroupAutoAttendantModifyInstanceRequest17sp1, we received two different XML files to try, one for William Goldenberg (what I believe be from a gen-I platform in New Zealand) and another from Aman in Australia from a platform 17sp4, We try to send this to XML files to your account and the XML’s didn’t complain.

We experiment with many changes to those files to try to find what is wrong. We changing names, users, encoding, minimizing the amount of information in the XML, added other parameters, etc. Aman in Australia try to help us for a whole day and We can’t make this schema to work.

We have been using the software we developed and also the software for tests we received from William ASOCISoapClient.rar. The results for this application is posted in the end this email.

Anyone have any ideas?

Best regards,

Icaro Lavrador

Hello,

A project ago we had to
roll 17 phones out, each with their own user on it. Since we are a small
business and not used to large roll-outs we began to wonder if there was an
easier way to create and roll-out. The question is probably really simple;

How to create users via
XSI?

This also includes creating devices and linking them to users.

I read through the
BSv19 XSI Reference book, but I was unable to find the answer.

I'm attempting to integrate with a VoiceXML webapp. This webapp requires some query string parameters. I've attempted to configure them as follows under the Profile-Addresses of the user that will connect to the webapp:

dialog@ms1.xdp.broadsoft.com;voicexml=http://<webapp-address>?param1=value1&param2=value2

This doesn't work. The query string parameters just get stripped off when the request is sent. Is there any way to do this using some other syntax? The VXML/CCXML Developers Guide only shows options for passing params to an actual script.

Im trying to update a channel via CTI to the sandbox, but the response I get indicates an erronoues request. I fail to see what is wrong with the request being sent, so any help would be much appreciated.

Request sent:

<?xml version="1.0" encoding="UTF-8"?><xsp:request xmlns:xsp="http://schema.broadsoft.com/XspXMLInterface" version="19.0"><requestId>1a16e4e6-d09e-4350-a5e9-8de4015d6ef1</requestId><sessionId>1112</sessionId><credentials>REMOVED</credentials><UpdateChannelRequest><uri>/com.broadsoft.xsi-events/v2.0/channel</uri><method>PUT</method><version/><params/><xsp:payload><Channel xmlns="http://schema.broadsoft.com/xsi"><channelId>9bdc0a4e-170d-46d7-8ff9-514a5899f1d6</channelId><expires>3600</expires></Channel></xsp:payload></UpdateChannelRequest></xsp:request>

Response:

<?xml version="1.0" encoding="UTF-8"?><xsp:response xmlns:xsp="http://schema.broadsoft.com/XspXMLInterface" version="17.0"><requestId>1a16e4e6-d09e-4350-a5e9-8de4015d6ef1</requestId><sessionId>1112</sessionId><statusCode>403</statusCode><reason>Forbidden</reason><xsp:payload><ErrorInfo xmlns="http://schema.broadsoft.com/xsi"><summary>XML schema validation failed: error: cvc-elt.3.1: Element has xsi:nil attribute but is not nillable in element OCICMessage@http://schema.broadsoft.com/oci-c&lt;oci:channelId xsi:nil="true" xmlns:oci="http://schema.broadsoft.com/oci-c" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/></summary><summaryEnglish>XML schema validation failed: error: cvc-elt.3.1: Element has xsi:nil attribute but is not nillable in element OCICMessage@http://schema.broadsoft.com/oci-c&lt;oci:channelId xsi:nil="true" xmlns:oci="http://schema.broadsoft.com/oci-c" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/></summaryEnglish><errorCode>102005</errorCode></ErrorInfo></xsp:payload></xsp:response>

Best Regards

Eirik Caspari