vaibhav3002 / sipdroid

Automatically exported from code.google.com/p/sipdroid
GNU General Public License v3.0
0 stars 0 forks source link

Packet address mismatch with connected address while making calls #750

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install Sipdroid in two different android phones (HTC Desire & HTC Wildfire)
2. Make call between them
3. Produces - java.lang.IllegalArgumentException: Packet address mismatch with 
connected address

What is the expected output? What do you see instead?
This error happens only when calling between 2 android phones. With one android 
phone and other phone(iPhone, IP phone, PSTN) works fine.

What version of the product are you using? On what device/operating system?
Android 2.2 - HTC

Which SIP server are you using? What happens with PBXes?
Voip Switch

Which type of network are you using?
WiFi

Please provide any additional information below.

E/AndroidRuntime( 4511): java.lang.IllegalArgumentException: Packet address 
mismatch with connected address
E/AndroidRuntime( 4511):        at 
java.net.DatagramSocket.send(DatagramSocket.java:436)
E/AndroidRuntime( 4511):        at 
org.sipdroid.net.SipdroidSocket.send(SipdroidSocket.java:65)
E/AndroidRuntime( 4511):        at 
org.sipdroid.net.RtpSocket.send(RtpSocket.java:85)
E/AndroidRuntime( 4511):        at 
org.sipdroid.media.RtpStreamSender.run(RtpStreamSender.java:461)

Original issue reported on code.google.com by vvellak...@gmail.com on 19 Nov 2010 at 12:42

GoogleCodeExporter commented 9 years ago
I recently got this error (and a force close) out of sipdroid going from 
CyanogenMod 6.1.1 to 7.0.0-RC1.  I suspect DatagramSocket.send() now throws 
this on certain conditions (like packet address wrong for socket) where it 
formerly threw an IOException (which sipdroid handles).

Original comment by jej...@googlemail.com on 24 Feb 2011 at 9:57

GoogleCodeExporter commented 9 years ago

Original comment by pmerl...@googlemail.com on 1 Mar 2011 at 9:28

GoogleCodeExporter commented 9 years ago
Rethrowing as an IOException fixes it for me at least on CM 7.0.0-RC1

Original comment by jej...@googlemail.com on 6 Mar 2011 at 3:12

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by pmerl...@googlemail.com on 25 Mar 2011 at 11:23