148
Views
0
Helpful
0
Comments

Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 05:24 PM
This document was generated from CDN thread
Created by: Jason Shaffer on 15-07-2013 09:49:37 AM
Hi Cisco Dev Team (And Thomas),
We are getting a fault code when we POST the following code:
This is what it's returning:
The Conference does exist and we've tried leaving the value blank as well as coming up with something random. Any guidance on what we are doing wrong?
Many Thanks!
-jason
-jason
Subject: RE: Fault Error on
Replied by: Thomas Bonhomme on 15-07-2013 03:23:59 PM
Hi Jason
Even if the doc. doesn't mention it for "participant.message" method, I would think that if the participant is in a conference, the call may require the conferenceName, and if the participant is in an autoattendant, the call may require the autoAttendantUniqueId instead. The call will not require both parameters.
Cheers,
Thomas
Subject: RE: Fault Error on
Replied by: Thomas Bonhomme on 15-07-2013 03:30:37 PM
In addition, I also see 2 another issues in your request: double space in the participant name and a typo in participantProtocol ;)
Created by: Jason Shaffer on 15-07-2013 09:49:37 AM
Hi Cisco Dev Team (And Thomas),
We are getting a fault code when we POST the following code:
1<?xml version="1.0" encoding="iso-8859-1"?>
2<methodCall>
3<methodName>participant.message</methodName>
4<params>
5 <param>
6 <value>
7 <struct>
8 <member>
9 <name>conferenceName</name>
10 <value>
11 <string>Conf01</string>
12 </value>
13 </member>
14 <member>
15 <name>autoAttendantUniqueID</name>
16 <value>
17 <string/>
18 </value>
19 </member>
20 <member>
21 <name>participantName</name>
22 <value>
23 <string>Stephen Weber</string>
24 </value>
25 </member>
26 <member>
27 <name>participantProtocal</name>
28 <value>
29 <string>sip</string>
30 </value>
31 </member>
32 <member>
33 <name>participantType</name>
34 <value>
35 <string>by_address</string>
36 </value>
37 </member>
38 <member>
39 <name>message</name>
40 <value>
41 <string>aaa</string>
42 </value>
43 </member>
44 <member>
45 <name>authenticationUser</name>
46 <value>
47 <string>admin</string>
48 </value>
49 </member>
50 <member>
51 <name>authenticationPassword</name>
52 <value>
53 <string>12345</string>
54 </value>
55 </member>
56 </struct>
57 </value>
58 </param>
59</params>
60</methodCall>
2<methodCall>
3<methodName>participant.message</methodName>
4<params>
5 <param>
6 <value>
7 <struct>
8 <member>
9 <name>conferenceName</name>
10 <value>
11 <string>Conf01</string>
12 </value>
13 </member>
14 <member>
15 <name>autoAttendantUniqueID</name>
16 <value>
17 <string/>
18 </value>
19 </member>
20 <member>
21 <name>participantName</name>
22 <value>
23 <string>Stephen Weber</string>
24 </value>
25 </member>
26 <member>
27 <name>participantProtocal</name>
28 <value>
29 <string>sip</string>
30 </value>
31 </member>
32 <member>
33 <name>participantType</name>
34 <value>
35 <string>by_address</string>
36 </value>
37 </member>
38 <member>
39 <name>message</name>
40 <value>
41 <string>aaa</string>
42 </value>
43 </member>
44 <member>
45 <name>authenticationUser</name>
46 <value>
47 <string>admin</string>
48 </value>
49 </member>
50 <member>
51 <name>authenticationPassword</name>
52 <value>
53 <string>12345</string>
54 </value>
55 </member>
56 </struct>
57 </value>
58 </param>
59</params>
60</methodCall>
This is what it's returning:
1{"faultCode":8,"faultString":"no conference name or auto attendant id supplied","status":"fail"}
The Conference does exist and we've tried leaving the value blank as well as coming up with something random. Any guidance on what we are doing wrong?
Many Thanks!
-jason
-jason
Subject: RE: Fault Error on
Replied by: Thomas Bonhomme on 15-07-2013 03:23:59 PM
Hi Jason
Even if the doc. doesn't mention it for "participant.message" method, I would think that if the participant is in a conference, the call may require the conferenceName, and if the participant is in an autoattendant, the call may require the autoAttendantUniqueId instead. The call will not require both parameters.
Cheers,
Thomas
Subject: RE: Fault Error on
Replied by: Thomas Bonhomme on 15-07-2013 03:30:37 PM
In addition, I also see 2 another issues in your request: double space in the participant name and a typo in participantProtocol ;)
Labels: