Menu

#509 Integration with Gingerbread

Duplicate
nobody
None
Medium
Defect
2011-02-09
2010-12-18
Anonymous
No

Originally created by: steve.lo...@gmail.com

Previously, I used CSIPSimple on a Nexus One 2.2.1 flawlessly; my SIP service is SIP Sorcery.

I'm setting up a Nexus S with Gingerbread 2.3, which, as you know, has a built-in SIP stack. I've discovered the following:

1) the built-in stack has considerable echo for my service; so

2) when I run CSIPSimple, the built-in stack seems to compete for calls. For example, when I place a call, first I'm asked whether I want to use the built-in stack or CSIPSimple, and then I'm asked whether I want to place the call with CSIPSimple or the cell dialer.

Someone with more experience than me, hopefully, can offer a more informed summary of the compatibility. Thanks for listening.

Related

Tickets: #452
Tickets: #699
Tickets: #796

Discussion

  • Anonymous

    Anonymous - 2010-12-19

    Originally posted by: r3gis...@gmail.com

    Lucky man ;)

    Well I've no Nexus S nor device with Gingerbread for now (and the emulator in 2.3 doesn't include the SIP feature).

    So everything I can say here are just suppositions :

    I think that when you make a call it send a "sip:" intent. (The good part is that I've already registered this intent :) ).
    The thing is that, exactly like other apps that provide the same service (manage "sip:" intents) android detect that there is two applications that can perform the intent. (It goes the same when you install 2 browsers, or when you send an email etc)

    However in theory, android in the first popup should allow you to remember your choice. (A little checkbox under the choice). If you select it and press CSipSimple, next time you'll not be asked anymore to choice between the native stack or CSipSimple.

    Besides, as soon as I'll get a device with gingerbread on it I'll do more fancy integration : see issue 452.
    I planned to have something really cool providing user the choice to switch a configured account in CSipSimple between the native and the pjsip SIP stack.
    As consequence we will also get within the CSipSimple chooser a mean to use the native stack, so no reason to keep the native stack as default choice (no reason to not tick the checkbox to remember the CSipSimple choice ;) )

    Mergedinto: 452
    Status: Duplicate

     

    Related

    Tickets: #452


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.