kamilpavlicko/de-tiny-sip

Automatically exported from code.google.com/p/de-tiny-sip

de-tiny-sip's Issues

Audio not working in TinySip

What steps will reproduce the problem?
1.Download tinysip 
2.Run the app
3.Call gets connected but no audio is heard 

What is the expected output? What do you see instead?
Audio must be heard (including the ringing state)

What version of the product are you using? On what operating system?
revision 1.2. Windows 7

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 20 Apr 2012 at 3:03

Delvik Cache Error

What steps will reproduce the problem?
1. Download the source from SVN
2. Import the project as an Android project in Eclipse
3. Try to Run it as an Android project.

What is the expected output? What do you see instead?
1. Run the example
2. [2012-10-04 11:17:58 - de.tinysip.sipdemo.TinySipDemoActivity] Dx 
trouble processing "javax/sip/header/OrganizationHeader.class":

Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.

This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.

However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.

If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.

If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.

If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.

[2012-10-04 11:17:58 - de.tinysip.sipdemo.TinySipDemoActivity] Dx 1 error; 
aborting
[2012-10-04 11:17:58 - de.tinysip.sipdemo.TinySipDemoActivity] Conversion to 
Dalvik format failed with error 1


What version of the product are you using? On what operating system?
Eclipse Indigo
Android SDK 2.3

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 4 Oct 2012 at 5:38

SIP invite is sending with Random port number rather than 5060

What steps will reproduce the problem?
1. source port number of the emulator for sip invite is random rather than 5060
2. so we are unable to receive 200ok for invite

Original issue reported on code.google.com by [email protected] on 18 Aug 2011 at 2:23

initialize the localsipport missing give value to sipport

What steps will reproduce the problem?
1. goto LocalSipProfile.java 
2. check public LocalSipProfile(String userName, String sipDomain, String 
sipPassword, int sipPort, String displayName) 
3. you could see 
                this(userName, sipDomain, sipPassword);
        this.displayName = displayName;


What is the expected output? What do you see instead?
     missing 
               this.sipport = sipPort

What version of the product are you using? On what operating system?
latest

Please provide any additional information below.

Original issue reported on code.google.com by Peter880313 on 14 Apr 2012 at 3:36

Error on SIP registration

I get the following error when i run the program:

11-12 11:28:45.030: W/System.err(30542): java.lang.NullPointerException
11-12 11:28:45.030: W/System.err(30542):    at 
de.tinysip.sip.SipManager.registerProfile(SipManager.java:116)
11-12 11:28:45.030: W/System.err(30542):    at 
de.tinysip.sipdemo.TinySipDemoActivity.startSipRegistration(TinySipDemoActivity.
java:234)
11-12 11:28:45.030: W/System.err(30542):    at 
de.tinysip.sipdemo.TinySipDemoActivity.onCreate(TinySipDemoActivity.java:102)
11-12 11:28:45.030: W/System.err(30542):    at 
android.app.Activity.performCreate(Activity.java:5008)
11-12 11:28:45.030: W/System.err(30542):    at 
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
11-12 11:28:45.030: W/System.err(30542):    at 
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2023)
11-12 11:28:45.038: W/System.err(30542):    at 
android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2084)
11-12 11:28:45.038: W/System.err(30542):    at 
android.app.ActivityThread.access$600(ActivityThread.java:130)
11-12 11:28:45.038: W/System.err(30542):    at 
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1195)
11-12 11:28:45.038: W/System.err(30542):    at 
android.os.Handler.dispatchMessage(Handler.java:99)
11-12 11:28:45.038: W/System.err(30542):    at 
android.os.Looper.loop(Looper.java:137)
11-12 11:28:45.038: W/System.err(30542):    at 
android.app.ActivityThread.main(ActivityThread.java:4745)
11-12 11:28:45.038: W/System.err(30542):    at 
java.lang.reflect.Method.invokeNative(Native Method)
11-12 11:28:45.038: W/System.err(30542):    at 
java.lang.reflect.Method.invoke(Method.java:511)
11-12 11:28:45.038: W/System.err(30542):    at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
11-12 11:28:45.038: W/System.err(30542):    at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
11-12 11:28:45.038: W/System.err(30542):    at 
dalvik.system.NativeStart.main(Native Method)

I have set up all the details in the settingsprovider.java to my server, yet 
still get this error.

Original issue reported on code.google.com by [email protected] on 12 Nov 2012 at 9:34

Can't Run on Emulator

What steps will reproduce the problem?
1. Checkout the project
2. Import into eclipse
3. Try to run as Android Project

What is the expected output? What do you see instead?
The emulator starts, launching SIP Demo

What version of the product are you using? On what operating system?
Latest checkout of TinySIP, latest eclipse, on linux

Please provide any additional information below.
Fails with error "conversion to dalvik format failed with error 1"

Original issue reported on code.google.com by [email protected] on 12 Apr 2012 at 7:26

Conversion to Dalvik format failed with error 1

What steps will reproduce the problem?
1. Checkout the source via SVN
2. Import the project in Eclipse
3. Try to launch TinySipDemoActivity

What is the expected output? What do you see instead?
Following the description, the TinySipDemo should run without further 
modification. In my case I receive a Conversion to Dalvik format failed with 
error 1. 

What version of the product are you using? On what operating system?

I am using Eclipse 3.7.2 on Windows 7 64 bit.

Please provide any additional information below.

Full console output:

[2012-03-30 10:33:47 - TinySip] Dx 
trouble processing "javax/sip/address/Address.class":

Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.

This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.

However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.

If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.

If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.

If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.

Original issue reported on code.google.com by [email protected] on 30 Mar 2012 at 9:17