Not able to make (E.164) number call from the WebEx Browser SDK

[kmarimuthu]

Hi,
I am trying to make Telephone number(E.164)  call from my WebEx calling user with using WebEx browser SDK application (https://developer.webex.com/docs/sdks/browser), but the call not initiating from WebEx browser SDK application.
 can I get the reason why the call is not initiating and please share , is there any way to make basic Telephony Call using WebEx SDKs ?

Thanks, and Regards,
Karthikeyan

[sandiban · Accepted solution]

Hi @kmarimuthu,
Thanks for your patience so far!
To answer your question, Webex Browser SDK is not suitable for Calling actually. Basically it doesn't have that Calling feature in it.
In that case, you should opt for Webex Web Calling SDK which is designed for Calling and you can find that details here - https://developer.webex.com/docs/sdks/webex-calling-sdk

Here is the corresponding GitHub link - https://github.com/webex/webex-js-sdk/wiki/Introducing-the-Webex-Web-Calling-SDK

Hope this should help you here.
Please let us know for any further queries.

Regards!
Sandip

[kmarimuthu]

Hi @sandiban , 

Thanks for the quick response, now I am able to make a  (E.164) number call (using https://github.com/webex/webex-js-sdk/wiki/Introducing-the-Webex-Web-Calling-SDK).
One more request, is there any option to get the call failure reason like "release cause" or "CDR Termination code" for validating the call routing using WebEx Web Calling SDK ? 

Thanks, and Regards,
Karthikeyan

[sandiban]

I don't think that's currently available @kmarimuthu !
However, there should be trackingId available with that error. If you could share that trackingId with us, we can check if that error description has that details in the Logs or, not.
if it's available from our internal log, then we can ask SDK team to make it more detailed taking data from the logs description.
That should help here I believe.
You can share the details to devsupport@webex.com in that case so that'd raise a case to our queue and we can track it further.
Thanks!

[kmarimuthu]

Hi @sandiban , 

Usually for the Normal WebEx Clients Application, we can able to see the XSI Events  which is getting logged in the WebEx application log file for every change in call state, in that the internalReleaseCause detail will be available for Call Relased Event.

In the similar way, can we get the XSI Event log using the SDK through any log listeners  or functions?

Sample XSI Event log for your reference,

2024-01-16T13:52:00.561Z <Info> [0x8614][]RequestManager.cpp:4350 bwc::xsi::RequestManagerPrivate::onEventChannelChunkReceived:BWC:INTERNAL: Event xml: <?xml version="1.0" encoding="UTF-8"?>
<Event xmlns="http://schema.broadsoft.com/xsi"
xmlns:ns0="http://www.w3.org/2001/XMLSchema-instance"
type="xsi:SubscriptionEvent">
<eventID>eb6896e3-6be3-4cdc-8a72-4d75d2589784</eventID>
<sequenceNumber>10</sequenceNumber>
<userId>{!1f70210e09621b45!}</userId>
<externalApplicationId>BWC_WIN_v2.0_ab79f884-a6ad-40fc-a647-2bf2976f34a2</externalApplicationId>
<subscriptionId>b3941e92-88ed-4041-97b6-8662db0d88b5</subscriptionId>
<channelId>b52d9c05-1a58-4ab2-822f-995181e1f174</channelId>
<eventData ns0:type="xsi:CallReleasedEvent">
<call>
<callId>callhalf-6436726035:0</callId>
<extTrackingId>777a3ce0-c364-4cec-8353-39ef192ddc8f</extTrackingId>
<personality>Originator</personality>
<state>Released</state>
<releaseCause>
<internalReleaseCause>Temporarily Unavailable</internalReleaseCause>
<cdrTerminationCause>111</cdrTerminationCause>
</releaseCause>
<remoteParty>
<name>{!d5d7eb03ddc86dc0!}</name>
<address>{!dce33f848b31fee1!}</address>
<userId>{!1c97284e46366f5e!}</userId>
<userDN countryCode="{!0dcc509a6f75849b!}">{!c2098cf8942350f0!}</userDN>
<callType>Group</callType>
</remoteParty>
<startTime>1705413180849</startTime>
<releaseTime>1705413196849</releaseTime>
</call>
</eventData>
</Event>

2024-01-16T13:52:00.561Z <Warn> [0x5f98][]uriparser.rl:267 TP::Sip::parseUri:BWC:INTERNAL: URI Invalid: {!564f037b09e8058e!}
2024-01-16T13:52:00.562Z <Info> [0x5f98][]transport_tcp.cpp:355 TP::Sip::TcpConnectionPtr::handleNext:BWC:INTERNAL: Writing response:

Thanks, and Regards,
Karthikeyan