Skip to content
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.

Failed to make calls from imsdroid to pc client using OpenIMSCore #33

Closed
GoogleCodeExporter opened this issue Apr 13, 2015 · 6 comments
Closed

Comments

@GoogleCodeExporter
Copy link

I tried to make a call from imsdroid to a pc client using Open IMS Core

Imsdroid is running on a real android 1.5 device which is connected to the 
internet (wifi) using a router, so it is behind nat.

The pc client I use is the MONSTER client. It is installed on the same pc that 
hosts the ims server. Calling from one pc to another works.

I also use a RTP Proxy on that pc.

Registration of imsdroid seems to work.

The problem is that I only have one way audio, from pc to mobile device.

Original issue reported on code.google.com by jorisn...@gmail.com on 17 Aug 2010 at 9:01

@GoogleCodeExporter
Copy link
Author

Could you please send the capture (at P-CSCF) with both the REGISTER and INVITE 
requests?

Original comment by boss...@yahoo.fr on 17 Aug 2010 at 11:23

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

I would suggest to test the same combo with all the firewalls off just to 
clarify the source of the problem - whether it is NAT or some sip 
misconfiguration

Original comment by volkov.r...@gmail.com on 17 Aug 2010 at 11:25

@GoogleCodeExporter
Copy link
Author

Thanks for the fast response. I have included the capture.
I don't think it's a firewall issue cause pc to pc calls work (with one pc on 
the same network as the mobile device).


Original comment by jorisn...@gmail.com on 18 Aug 2010 at 1:52

Attachments:

@GoogleCodeExporter
Copy link
Author

I think you are behind a NAT or something like this. Why do you get 403 
responses for SUBSCRIBE and PUSBLISH requests? Is it possible to have the 
wireshark file instead of a txt?
There is an issue on OpenIMSCore. This is discussed here: 
http://lists.berlios.de/pipermail/openimscore-users/2010-August/006362.html

Original comment by boss...@yahoo.fr on 19 Aug 2010 at 1:05

@GoogleCodeExporter
Copy link
Author

I can take a look at it again on monday. I shall try to get you a wireshark 
file and figure out where the 403 respones come from. 

Thanks for helping

Original comment by jorisn...@gmail.com on 20 Aug 2010 at 3:43

@GoogleCodeExporter
Copy link
Author

Original comment by boss...@yahoo.fr on 7 Sep 2010 at 1:57

  • Changed state: Fixed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant