jannies
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by jannies
-
-
Hi,
We are trying to access the API documentation site but are receiving an error.
-
If you can give an example of "native" CSTA we can look into it. We do not specialize in CSTA and do not have any knowledge other than what we have done here.
-
We have changed the HTTP post to the host(domain) and removed the @domain after username and still the same error. We also tried to specify the domain in the MakeCall soap request node with no luck.
POST / HTTP/1.1
Content-Type: application/xml
Host: pbx.nhb.co.za
Content-Length: 324
Expect: 100-continue
Connection: Keep-Alive
HTTP/1.1 100 Continue
<?xml version="1.0" standalone="yes"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sns="http://www.pbxnsip.com/soap/pbx"><env:Body><sns:MakeCall><domain></domain><callingDevice>8025</callingDevice><calledDirectoryNumber>082********</calledDirectoryNumber></sns:MakeCall></env:Body></env:Envelope>HTTP/1.1 500 Internal Server Error
Content-Type: application/xml
Content-Length: 583
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope" xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed4"><SOAP-ENV:Body><SOAP-ENV:Fault><SOAP-ENV:faultcode>Client</SOAP-ENV:faultcode><SOAP-ENV:faultstring>CSTA Error</SOAP-ENV:faultstring><SOAP-ENV:detail><csta:CSTAErrorCode xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed4"><csta:operation>invalidCalledDeviceID</csta:operation></csta:CSTAErrorCode></SOAP-ENV:detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope> -
That is correct. Our unit test for making a call using CSTA works perfectly on version 60 but fails with the above error on the latest 61.0.2
-
Hi
We have been using the CSTA MakeCall since the last post on this topic in 2012
We are in process of upgrading our Vodia pbx from 60 to 61 and in this functionality is now giving a similar error although we have not changed anything:
See the full trace below:
POST / HTTP/1.1
Content-Type: application/xml
Host: 192.168.x.x
Content-Length: 338
Expect: 100-continue
Connection: Keep-Alive
HTTP/1.1 100 Continue
<?xml version="1.0" standalone="yes"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sns="http://www.pbxnsip.com/soap/pbx"><env:Body><sns:MakeCall><domain></domain><callingDevice>8025@pbx.ourdomain.co.za</callingDevice><calledDirectoryNumber>0820000000</calledDirectoryNumber></sns:MakeCall></env:Body></env:Envelope>HTTP/1.1 500 Internal Server Error
Content-Type: application/xml
Content-Length: 583
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope" xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed4"><SOAP-ENV:Body><SOAP-ENV:Fault><SOAP-ENV:faultcode>Client</SOAP-ENV:faultcode><SOAP-ENV:faultstring>CSTA Error</SOAP-ENV:faultstring><SOAP-ENV:detail><csta:CSTAErrorCode xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed4"><csta:operation>invalidCalledDeviceID</csta:operation></csta:CSTAErrorCode></SOAP-ENV:detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>PBX LOG File
8] 20:41:47.527 SOAP: SOAP: Request from IP address 192.168.0.0 without a session [5] 20:41:47.534 SOAP: Receive SOAP request via HTTP interface <?xml version="1.0" standalone="yes"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sns="http://www.pbxnsip.com/soap/pbx"><env:Body><sns:MakeCall><domain></domain><callingDevice>8025@pbx.mydomain.co.za</callingDevice><calledDirectoryNumber>0820000000</calledDirectoryNumber></sns:MakeCall></env:Body></env:Envelope>
-
We have been using the CDR URL to post json for quite some time and every now and then the posting stops working. This includes the action URL end points for "When a new call comes in" and "When a call connects to an agent"
The log file shows that that requests are pending up and till it reaches 500 where it then starts to drop the webclient requests.
[5] 2018/05/03 15:23:58: Action URL request http://xxxapi.xxx.co.za/api/CreateNewCall{
"id":"1326",
"from":"\"xxxx\" <sip:8062@pbx.xxx.co.za>",
"to":"\"xxx\" <sip:8028@pbx.xxx.co.za>",
"callid":"5aeb0d7c222b-n3vc93jb8p6v",
"domain":"pbx.xxx.co.za",
"lang":"",
"clip":"false",
"extension":"8062",
"trunk": "",
"source": "[source}",
"target": "8028"
}
[6] 2018/05/03 15:23:58: 500 more requests pending to xxxapi.xxx.co.za:80[2] 2018/05/03 15:23:58: Too many webclient requests, dropping http://xxxapi.xxx.co.za:80/
-
Unfortunately when i tested the above i had my VPN connection on and only realised this now when trying to test this again.
I still think we have a NAT problem but what i do not understand is this do not want to work internally now. When using chrome's WebRTC Internals it seems that it is now trying to use the external IP configured in the IP Routing List when we are coming from an internal IP and this information is coming from googles stun server (stun:stun.l.google.com:19302). See attached image.
Any clarity on how this works would be appreciated.
-
Thank you, we setup the IP Routing List as described in the link and it solved the problem.
-
We have managed to use the user web dialer to make calls and is working 100% within our LAN network.
When performing the same from externalyl the actual call is initiated but no voice or ringing. When we run wireshark on the desktop we can see the that there is STUN traffic trying to connect to the internal IP address of the PBX server which is obviously not reachable from external.
Is there any configuration that has to happen so the web dialer knows to use the referring uri or IP instead?
-
We are receiving JSON cdr posts from our Vodia 56.5 PBX and are experiencing time differences between local time and the other time fields. The only time that is correct is LocalTime.
All the timezones are set to CAT+2 including Server timezone, admin timezone and domain timezone.
See sample data from the JSON post:
"TimeStart":"2017-09-04 12:21:18","TimeConnected":"2017-09-04 12:21:18","TimeEnd":"2017-09-04 12:21:51","LocalTime":"2017-09-04 14:21:18",
-
Hi
We have been testing CSTA MakeCall for some time and all of a sudden we are receiving an error "Invalid header(s): To" from our sip Gateway device. It seems the domain gets appended twice behind the number to be dialed. We have been testing this functionality for weeks and this problem started happening yesterday.
Please see partial call log below:
[5] 2012/06/06 11:56:21: SIP Tx udp:192.168.0.19:5060:
INVITE sip:0718961395@192.168.0.19;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.0.12:5060;branch=z9hG4bK-23ddcf1f2f619a06a96c113862f8dc5b;rport
From: <sip:8025@192.168.0.12;user=phone>;tag=687137098
To: <sip:0718961395@192.168.0.12@192.168.0.12;user=phone>
Call-ID: 739682a1@pbx
CSeq: 22373 INVITE
Max-Forwards: 70
Contact: <sip:play@192.168.0.12:5060;transport=udp>
Supported: 100rel, replaces, norefersub
Allow-Events: refer
Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE
Accept: application/sdp
User-Agent: snomONE/2011-4.5.0.1050 Coma Berenicids
P-Asserted-Identity: "ECN" <sip:play@192.168.0.19>
P-Charging-Vector: icid-value=;icid-generated-at=192.168.0.12;orig-ioi=192.168.0.12
Content-Type: application/sdp
Content-Length: 384
v=0
o=- 1384158937 1384158937 IN IP4 192.168.0.12
s=-
c=IN IP4 192.168.0.12
t=0 0
m=audio 28552 RTP/AVP 18 0 8 9 2 3 101
a=rtpmap:18 g729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:9 g722/8000
a=rtpmap:2 g726-32/8000
a=rtpmap:3 gsm/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=rtcp-xr:rcvr-rtt=all voip-metrics
a=sendrecv
[5] 2012/06/06 11:56:21: SIP Rx udp:192.168.0.19:5060:
SIP/2.0 400 Bad Request
Via: SIP/2.0/UDP 192.168.0.12:5060;branch=z9hG4bK-23ddcf1f2f619a06a96c113862f8dc5b;rport
From: <sip:8025@192.168.0.12;user=phone>;tag=687137098
To: <sip:0718961395@192.168.0.12@192.168.0.12;user=phone>
Call-ID: 739682a1@pbx
CSeq: 22373 INVITE
Server: Patton SN4960 4E30VRD 00A0BA073946 R5.7 2011-05-13 H323 RBS SIP M5T SIP Stack/4.0.30.30
Content-Type: text/plain
Content-Length: 21
Invalid header(s): To
************************************************************
The CSTA Soap conversation:
POST / HTTP/1.1
Content-Type: application/xml
Host: 192.168.0.12
Content-Length: 337
Expect: 100-continue
Connection: Keep-Alive
<?xml version="1.0" standalone="yes"?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sns="http://www.pbxnsip.com/soap/pbx"><env:Body><sns:MakeCall><domain></domain><callingDevice>8025@192.168.0.12</callingDevice><calledDirectoryNumber>0718961395</calledDirectoryNumber></sns:MakeCall></env:Body></env:Envelope>
HTTP/1.1 200 Ok
Content-Type: application/xml
Content-Length: 418
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope" xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed4"><SOAP-ENV:Body><csta:MakeCallResponse><csta:callingDevice><csta:callID>7f9bfbe1@pbx</csta:callID><csta:deviceID>8025@192.168.0.12</csta:deviceID></csta:callingDevice></csta:MakeCallResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
-
I assume 192.168.0.12 does not have 'localhost' as the alias.
So, try adding @domain name for the calling device & called devices. Ex: 8024@192.168.0.12.
Make sure that 192.168.0.12 is the domain name for 8024 & 8025.
Thanks very much.
This resolved my issue.
-
Hi
I have tested this functionality on a snom ONE free version and it works fine, but when trying to get it working on our production pbx i get the same error as above.
Both environments are running version 2011-4.5.0.1050.
I have tried the above mentioned suggestions with no luck.
Below is the soap conversation of the snom ONE free version that works fine.
POST / HTTP/1.1
Content-Type: application/xml
Host: 172.16.10.76
Content-Length: 326
Expect: 100-continue
<?xml version="1.0" standalone="yes"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sns="http://www.pbxnsip.com/soap/pbx">
<env:Body>
<sns:MakeCall>
<domain>172.16.10.76</domain>
<callingDevice>49</callingDevice>
<calledDirectoryNumber>41</calledDirectoryNumber>
</sns:MakeCall>
</env:Body>
</env:Envelope>HTTP/1.1 200 Ok
Content-Type: application/xml
Content-Length: 413
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope" xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed4">
<SOAP-ENV:Body>
<csta:MakeCallResponse>
<csta:callingDevice>
<csta:callID>0b36f9a3@pbx</csta:callID>
<csta:deviceID>49@localhost</csta:deviceID>
</csta:callingDevice>
</csta:MakeCallResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
And here is the conversation of the production server:
POST / HTTP/1.1
Content-Type: application/xml
Host: 192.168.0.12
Content-Length: 330
Expect: 100-continue
Connection: Keep-Alive
<?xml version="1.0" standalone="yes"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sns="http://www.pbxnsip.com/soap/pbx">
<env:Body>
<sns:MakeCall>
<domain>192.168.0.12</domain>
<callingDevice>8024</callingDevice>
<calledDirectoryNumber>8025</calledDirectoryNumber>
</sns:MakeCall>
</env:Body>
</env:Envelope>
HTTP/1.1 500 Internal Server Error
Content-Type: application/xml
Content-Length: 583
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope" xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed4">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<SOAP-ENV:faultcode>Client</SOAP-ENV:faultcode>
<SOAP-ENV:faultstring>CSTA Error</SOAP-ENV:faultstring>
<SOAP-ENV:detail>
<csta:CSTAErrorCode xmlns:csta="http://www.ecma-international.org/standards/ecma-323/csta/ed4">
<csta:operation>invalidCalledDeviceID</csta:operation>
</csta:CSTAErrorCode>
</SOAP-ENV:detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Even if i make all the fields blank the error stays the same.
Hope someone can help.
Wallboard & Daily Queue status Email report diffrence
in Web Interface
Posted
We are trying to understand why the ACD and Wallboard API the Other Redirected Calls are excluding from being subtracted to calculate the connected value.
In the daily email sent for that queue stats it is included.