pbxes and incoming calls

[GoogleCodeExporter]

outgoing calls with pbxes and sipgate works great. but incoming call via
pbxes doesn't work. can someone help me?

Original issue reported on code.google.com by xdowne...@gmail.com on 5 May 2009 at 4:10

[GoogleCodeExporter]

I have a similar issue:
Here are my logs from pbxes.org
2009-05-05      19:57:43    "anonymous"     1000    sipga­te.de    sipgate.de  
    ext-local  
Congestion      00:00:00        
    2009-05-05  19:56:52    "anonymous"     1000    sipga­te.de    sipgate.de  ext-local   Dial 
00:00:00        
    2009-05-05  19:52:29    "anonymous"     s   sipga­te.de    sipgate.de 
from-pstn-reghours-nofax    Hangup  00:00:00        
    2009-05-05  19:51:47    "anonymous"     s   sipga­te.de    sipgate.de 
from-pstn-reghours-nofax    Hangup  00:00:00    

Original comment by thesmi...@gmail.com on 5 May 2009 at 6:58

[GoogleCodeExporter]

Did you set up an inbound route?

Original comment by pmerl...@googlemail.com on 5 May 2009 at 7:33

[GoogleCodeExporter]

Same problem.  An X-Lite soft-phone configured on the same ring group as 
sipdroid is
able to receive incoming calls, while sipdroid has trouble.

Incoming calls do appear to work on sipdroid via pbxes if the incoming call is 
made
immediately after terminating an outgoing call from sipdroid.

Original comment by john.kie...@gmail.com on 5 May 2009 at 7:41

[GoogleCodeExporter]

yes, default inbound route is set up, also tried inbound route with Trunk ID 
set to 
sipgate.de

Original comment by thesmi...@gmail.com on 5 May 2009 at 8:11

[GoogleCodeExporter]

You need to set up as described at 
[http://www3.pbxes.com/community.php?display=wiki 
Fixed Mobile Convergence]. See 3.2 Call forwarding/forking.

Original comment by pmerl...@googlemail.com on 5 May 2009 at 8:26

[GoogleCodeExporter]

But with call-forwarding I'll get a regular incoming call again, right? Does 
SIPdroid 
not allow incoming SIP calls?

Original comment by thesmi...@gmail.com on 5 May 2009 at 8:30

[GoogleCodeExporter]

Call forwarding is great when there is no connection available, but when 
sipdroid is
connected to pbxes, incoming calls should work - but at this point, incoming 
calls
don't reliably make it through to sipdroid.

Original comment by john.kie...@gmail.com on 5 May 2009 at 10:45

[GoogleCodeExporter]

Incoming SIP calls take priority on incoming regular calls. They can be 
identified by 
the turquoise icon in the status bar. Pressing the menu button answers the SIP 
call. 
Pressing the green call button would answer the regular call.

Original comment by pmerl...@googlemail.com on 6 May 2009 at 11:21

[GoogleCodeExporter]

Issue 18 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 6 May 2009 at 11:22

[GoogleCodeExporter]

I dont know why issue 18 been merged to this one. Maybe i'm to stupid to find 
the
answer here.
My problem is the notification on an incoming call. My HTC Magic receives the 
call
with the standard "incoming-call-window". But there is no ringtone or something 
else.
If the display is black(inactive) it stay black. So its impossible to recognize 
an
incoming call.

Original comment by fheind...@gmail.com on 6 May 2009 at 12:28

[GoogleCodeExporter]

I do not receive notification of an incoming sip call on sipdroid, unless I have
recently (within the last min.) made an outgoing sip call.  Even if I keep the 
phone
awake with the sipdroid application having focus, I will not receive 
notification,
nor do I have any way to answer, an incoming sip call.

The only way for me to receive any type of notification of an incoming sip call 
is to
have made an outgoing sip call in the last minute.

FYI: The sipdroid status is green/connected at all times while testing, and I 
can
make outgoing calls without trouble.

Original comment by john.kie...@gmail.com on 6 May 2009 at 1:04

[GoogleCodeExporter]

A parallel call needs to be set up to get incoming calls.

Original comment by pmerl...@googlemail.com on 6 May 2009 at 1:23

[GoogleCodeExporter]

Can you expand on this "parallel call" requirement please?

I must be wrong here, but it seems like you're passing this off as "by design".

Original comment by john.kie...@gmail.com on 6 May 2009 at 2:33

[GoogleCodeExporter]

I think "parallel call" is to place two calls :
one to the SIP account and one to the mobile phone number,
on asterisk I've do a Dial(SIP/myphonenumber@myprovider&SIP/mysipextension)
so when a SIP call start, a mobile phone call start to and my HTC Dream Ring.
now it's work fine.just 10 seconds more of delay.

Original comment by jpg...@yahoo.fr on 6 May 2009 at 3:39

[GoogleCodeExporter]

I see.

Configuring my sipdroid extension in pbxes to also "fork" to my cell number 
seems to
now alert sipdroid to check if it also has an incoming call.

Convoluted, but it works.

Having to remember to look for the "turquoise icon", then remember to hit menu 
to
answer it certainly takes some getting used to.  Remembering to hit the back 
button
to end a sip call has been equally as difficult to acclimate.

Original comment by john.kie...@gmail.com on 6 May 2009 at 4:13

[GoogleCodeExporter]

Same here -- with forking incoming calls on Sipdroid works --- is this a 
temporary
"restriction" or by design that this is necessary?

Original comment by thesmi...@gmail.com on 7 May 2009 at 9:49

[GoogleCodeExporter]

Issue 19 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 7 May 2009 at 1:11

[GoogleCodeExporter]

Two problems I see with using a forked call to the mobile number as a trigger 
to have
sipdroid check for incoming calls:

1) Unable to tell if incoming call is from sip or pots (and as a result, if one
should press the green answer button to answer the pots call, or the menu 
button to
answer the sip call) until the turquoise icon appears.  In many cases, it can 
take a
few rings on the pots/mobile number before sipdroid has been able to detect if 
there
is a sip call.  Now you need to stare at your phone for a few rings on each 
incoming
call, instead of just answering the darn thing.

2) If you are out of cell coverage range (for example, indoors in a poor 
coverage
area), relying on wifi/sip for calls, you now have no way to trigger sipdroid to
"poll" for incoming sip calls, since your pots/mobile number will be unable to 
reach
you to trigger the sip poll.

Original comment by john.kie...@gmail.com on 7 May 2009 at 1:43

[GoogleCodeExporter]

Good idea. A mode could be added for polling (every 15 seconds) if out of cell 
but 
within wifi coverage.

Running such a mode for case 1) would be too battery expensive. Our tests 
indicated 
that standby times would be reduced to half a day.

Original comment by pmerl...@googlemail.com on 7 May 2009 at 5:04

[GoogleCodeExporter]

Running Gmail on the phone, I seem to get notifications of email deliveries 
rather
quickly.  Because of this, some thoughts come to mind:

1) How is the Gmail client being notified of deliveries without draining the 
battery
so much?

2) Is the way Gmail receives quick notifications applicable to SIP?

Original comment by john.kie...@gmail.com on 7 May 2009 at 7:39

[GoogleCodeExporter]

Hi. Im trying to set up the call forking/forwarding in pbxes.org and I have no
success so far. I tried to alter my incoming route with:
at "SIP URI:"
SIP/my_number@pbxes.org&SIP/my_sip_number

What am I doing wrong?

Is there an other free pbx service where this works?

Nice software btw :)

Best regards / Martin

Original comment by martin.l...@gmail.com on 8 May 2009 at 1:47

[GoogleCodeExporter]

I forgot to tell that I tested to call my_number@pbxes.org on the g1 and that 
works,
so the outbound route should be OK.

Original comment by martin.l...@gmail.com on 8 May 2009 at 1:49

[GoogleCodeExporter]

In the extensions setting on pbxes.org, add your mobile pstn (not sip) number 
in the
"Call Forking" area.  Make sure you have an incoming route passing your incoming
trunk(s) to the extension your sipdroid client is using.

I assume you can call pstn numbers with the outbound trunk you're using on 
pbxes.org?

Original comment by john.kie...@gmail.com on 8 May 2009 at 3:51

[GoogleCodeExporter]

Could Please Someone tell me how to hear an incoming call from sipdroid?

Original comment by vekexa...@gmail.com on 12 May 2009 at 5:45

[GoogleCodeExporter]

Wouldn't it be better for sipdroid to use the CRLF keep alive technique? Surely 
this
wouldn't affect battery life too much?

Original comment by simonnjs...@googlemail.com on 13 May 2009 at 12:14

[GoogleCodeExporter]

My understanding is that, with a little work, you can keep a TCP port open on 
android
with little effect on battery life (the way the Gmail client does it). However, 
"keep
alive" data should not be sent on this connection, since this will decrease 
battery
life.  The TCP server should only "push" data down when it needs the client to 
act
(like in this case, to notify the client of an incoming call).  The incoming 
data can
wake the client application, giving it a chance to act.

Original comment by john.kie...@gmail.com on 13 May 2009 at 12:40

[GoogleCodeExporter]

I cant get the call forking to work properly. When I watch the panel on 
pbxes.org I
can see the forking, but after a second or two, the incoming sip to G1 is lost 
and
only the forked call goes threw to the G1. I use gizmo5 as trunk. Could it be a 
codec
problem when forking? Please tell me with which providers, you had success.

Original comment by martin.l...@gmail.com on 13 May 2009 at 1:34

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

As John commented use the Call Forking field on the extension page. Don't set 
up a 
ring group for the forking.

Original comment by pmerl...@googlemail.com on 13 May 2009 at 8:06

[GoogleCodeExporter]

Parallel ringing does not work in 0.9.4. As a matter of fact, my phone does not 
ring
when you call it via SIP or PTSN. or PTSN&SIP at the same time.

There is no call notification what-so-ever when SIPROID is REGISTED TO THE 
SERVER!!

Original comment by vreme...@gmail.com on 13 May 2009 at 9:23

[GoogleCodeExporter]

Re Comment 23  by john.kielkopf

I have everything set up as it should be, I think.

With the callforking field set to my mobile number in the extension that goes 
to the
G1 sip account on pbxes.org

Still when i call the extension there is a 1 second SIP call to the G1 that is 
then
dropped and then the mobile # starts to ring on the G1. But with no SIP call 
anymore.

I think this might be a problem with pbxes.org and not with the Sipdroid 
software.

It would be nice to have a setting to run Sipdroid in a battery hungry way, but 
at
least working.

I use Gizmo5 as trunk.

Did anyone have success using Gizmo5 as a trunk?

Please mail a your successful setup, so I can start working with the operators 
that work.

Best regards / Martin

Original comment by martin.l...@gmail.com on 14 May 2009 at 3:41

[GoogleCodeExporter]

The problem with Gizmo is that it answers the call to your mobile too early. So 
call 
forking is stopped and connected to your mobile number. Maybe there is a 
setting 
within Gizmo that controls this. Otherwise you need another provider to call 
your 
mobile.

Original comment by pmerl...@googlemail.com on 14 May 2009 at 4:35

[GoogleCodeExporter]

So can you recommend a working trunk?

Original comment by martin.l...@gmail.com on 14 May 2009 at 5:33

[GoogleCodeExporter]

Have you seen the trunk recommendations by PBXes when you click on "Trunks" on 
the 
left?

Original comment by pmerl...@googlemail.com on 14 May 2009 at 5:42

[GoogleCodeExporter]

Now without Gizmo5 it works :)   Time for some more testing...  Thanks for the 
hints
everyone.

Cheers / Martin

Original comment by martin.l...@gmail.com on 15 May 2009 at 2:54

[GoogleCodeExporter]

Is incoming call notification a planned feature? I imagine there are more than 
a few
users who want to use their G1 without a SIM or without pbxes.org and thus 
can't rely
on the call forking to trigger an incoming call warning.

Original comment by jas...@gmail.com on 20 May 2009 at 5:38

[GoogleCodeExporter]

After some time of playing around with pbxes and sipdroid I figuered out how to 
set
the whole thing up and it works, but I can't receive calls. A short time after 
I've
calles someone (and he/she answered) it is possible, but for me forking is not
working as for some reason the G1 doesn't accept incomming calls on my 
UMTS-only SIM.
The reason I'm surprised about that is because my last phone at least told me 
that
there is an incomming call, but I cannot answer it.
After all that means I'm not really able to receive calls, so I hope they will
implement call notification.
Still, this programm really helped me and I love it.

Original comment by bastian....@googlemail.com on 27 May 2009 at 4:34

[GoogleCodeExporter]

Another thing on incoming calls, is that if your charging your phone, the led 
won't
change to "incoming call". The only thing to see if someone's calling, is to 
look at
the screen in this case. I'd guess that the "charging" led is mandatory, or 
something
else (i'm just a user in this case, with some Asterisk experience).

Like "jashsu" says, I want to use it without pbxes.org, but at this moment i'd 
only
can use Asterisk without a password, so I choose the secure way.

Original comment by erstaate...@gmail.com on 31 May 2009 at 9:41

[GoogleCodeExporter]

Issue 38 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 1 Jun 2009 at 8:01

[GoogleCodeExporter]

Ok, so... sipdroid does not ring or vibrate on incomming call. Here's a quick 
hack to
at least vibrate (for 5 seconds) on incoming call. If affected people could 
test it?

Plus... perhaps this should be called "BUILD.txt" to help people building 
sipdroid
without ide?

android update project -p . -t 2
ant

Original comment by zblab...@gmail.com on 4 Jun 2009 at 10:59

[GoogleCodeExporter]

This patch adds vibrate functionality. (Ok, feel free to remove 
"DeadObjectException
line").

Testing welcome.

Original comment by zblab...@gmail.com on 4 Jun 2009 at 11:00

Attachments:

• delme

[GoogleCodeExporter]

I'm willing to, but can you provide a small tutorial to accomplish this ?
cheers

Original comment by tugac...@gmail.com on 4 Jun 2009 at 5:10

[GoogleCodeExporter]

Issue 42 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 5 Jun 2009 at 6:54

[GoogleCodeExporter]

I added zblabunk as member. Please commit your change to trunk. I can review 
and 
build it next week.

Original comment by pmerl...@googlemail.com on 5 Jun 2009 at 7:03

• Changed state: Started

[GoogleCodeExporter]

Ok, thanks for account. Patch commited, but it may be a little too primitive.

Would it be ok to commit simple BUILD.txt file, explaining how to build 
sipdroid from
command line?

Original comment by zblab...@gmail.com on 8 Jun 2009 at 12:39

[GoogleCodeExporter]

Issue 47 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 9 Jun 2009 at 2:21

[GoogleCodeExporter]

Thanks for your first attempt for a fix. I improved it a little bit and built 
into 
0.9.6. Go ahead with the BUILD.txt.

Original comment by pmerl...@googlemail.com on 10 Jun 2009 at 11:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Issue 50 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 11 Jun 2009 at 12:34