Jingle is used for "signaling" - that is negotiating who will participate in the call, how to connect it (which IPs and ports) and what audio/video codecs will be use) WebRTC is used for actual audio/video exchange.

However, the logcat: org.webrtc.Logging: NetworkMonitorAutoDetect: Unable to obtain permission to request a cellular network.

How can i resolve the audio call?

And when the audio call was called, the PM Emulator got the error.

What is the question? What are you trying to do?

Are you trying to run Stork in the emulator?

"org.webrtc.Logging: NetworkMonitorAutoDetect: Unable to obtain permission to request a cellular network." - it seems that you haven't granted application all required permissions.

I tried to debug the audio call with in the emulator. And then something went wrong.

1. Unable to obtain permission to request a cellular network
2. When the audio call was called, the PM Emulator got the error.
3. the Jingle returned the feature_not_supported.

And the IscServers : "stun:stun.l.google.com:19302", "stun:stun1.l.google.com:19302", "stun:stun2.l.google.com:19302", "stun:stun3.l.google.com:19302", "stun:stun4.l.google.com:19302", "stun:stunserver.org:3478"

I can not telnet the port. Is that why I am in China.

The debugging process is like this：

But, the jingle has occurred a error on initiateSession, the response stanza such as:

8F:91:65:2D:A5:D7:7F:F5:49:88:C7:20:47:39:06:A9:20:4B:89:F8:10:5C:8D:51:4E:78:C3:7D:60:83:D5:9C8F:91:65:2D:A5:D7:7F:F5:49:88:C7:20:47:39:06:A9:20:4B:89:F8:10:5C:8D:51:4E:78:C3:7D:60:83:D5:9CThe feature is not supported yet.

Those ports are UDP so telnet will not work. I'm not familiar with China's restrictions related to accessing other servers.

Please help me analyze that the Jingle returned the feature_not_supported with initiateSession. Help me out , thanks a lot!

the tigase-server return the error: "<"error code="501" type="cancel"> "<"feature-not-implemented xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"> "<"text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" xml:lang="en">The feature is not supported yet. "<"/error>

It may happen that China block Google's stun servers - we can't help with that.

501 feature-not-implemented error most likely comes from your other user as Jingle is inherently client-client protocol. In this case its not the Tigase that sent the error but the other client.

I started two simulators with stork.It shouldn't have happened.

“<”iq xmlns="jabber:client" from="test1@xmpp.server" id="xWdvv29tr0gIIHIRcQJFEra" type="error" to="test2@xmpp.server/stork"> “<”jingle xmlns="urn:xmpp:jingle:1" initiator="test2@xmpp.server/stork" sid="BS3h3eICwjWj6ElT6lY3s9H" action="session-initiate"> ..........

Won't jingle XML go through tigase？

I'd recommend checking server logs - whether the message was correctly routed to the other client or not and if not, what was the issue.

The reason for this error is that the recipient's resource is null.

How to resolve it?

All <iq/> stanzas sent to bare JID (without resource) are responded by the server on behalf of the recipient. The only thing to fix that would be to sent <iq/> to the full JID (with a resource).

I know this method, but how to deal with it if it is multi client Online. Will Stork fix this problem?

That needs to be fixed in the client.

Will your stork fix this problem？However， how to solve the another about sending IQ with multi client Online?

There are two options:

• send IQ to all connected clients which you want to ring/call
• use XEP-0353: Jingle Message Initiation (however, it's not supported by the Stork yet -- we do accept PullRequests though)