I've been able to implement VoIP with multitasking, i.e., my application keeps running in the background, and notifies the user when there's an incoming call, using LocalNotifications.
The strange issue that I find is, this works only when I have my debugger running.
1. When I 'Build and Debug', with some breakpoints at the incoming voip call notification handlers in my app., it reaches there, and then goes on fine.
2. When I 'Build and Run' (disabled breakpoints), this point is not reached (I found out through the console logs).
Strangely, when I 'Enable' and then 'Disable' breakpoints, then the application is waken up by the system, and I get the notifications.
After this, notifications keep coming even in the background.
3. When I run the app stand-alone on the device, nothing works, but the application is not suspended, and when I switch back to my application, the notifications come.
I've tried this on all the beta releases, and the final GM release. Its the same.
I've done the voip and audio property setting in the plist and sockets configurations for voip.
The documentation says,
"When you configure a stream for VoIP, the system takes over management of the underlying socket. If new data arrives, the system wakes up your applicationl".
This happens for me, only with that debugger stuff.
Not when its running standalone on the device.
I've been able to implement VoIP with multitasking, i.e., my application keeps running in the background, and notifies the user when there's an incoming call, using LocalNotifications.
The strange issue that I find is, this works only when I have my debugger running.
1. When I 'Build and Debug', with some breakpoints at the incoming voip call notification handlers in my app., it reaches there, and then goes on fine.
2. When I 'Build and Run' (disabled breakpoints), this point is not reached (I found out through the console logs).
Strangely, when I 'Enable' and then 'Disable' breakpoints, then the application is waken up by the system, and I get the notifications.
After this, notifications keep coming even in the background.
3. When I run the app stand-alone on the device, nothing works, but the application is not suspended, and when I switch back to my application, the notifications come.
I've tried this on all the beta releases, and the final GM release. Its the same.
I've done the voip and audio property setting in the plist and sockets configurations for voip.
The documentation says,
"When you configure a stream for VoIP, the system takes over management of the underlying socket. If new data arrives, the system wakes up your applicationl".
This happens for me, only with that debugger stuff.
Not when its running standalone on the device.
Any ideas.
Hi akashthambiran,
I would like to ask you that which SDK you have used for VOIP development for iPhone. I want to develop VOIP application for iPhone but I am worried which SDK to use.
I've been able to implement VoIP with multitasking, i.e., my application keeps running in the background, and notifies the user when there's an incoming call, using LocalNotifications.
The strange issue that I find is, this works only when I have my debugger running.
1. When I 'Build and Debug', with some breakpoints at the incoming voip call notification handlers in my app., it reaches there, and then goes on fine.
2. When I 'Build and Run' (disabled breakpoints), this point is not reached (I found out through the console logs).
Strangely, when I 'Enable' and then 'Disable' breakpoints, then the application is waken up by the system, and I get the notifications.
After this, notifications keep coming even in the background.
3. When I run the app stand-alone on the device, nothing works, but the application is not suspended, and when I switch back to my application, the notifications come.
I've tried this on all the beta releases, and the final GM release. Its the same.
I've done the voip and audio property setting in the plist and sockets configurations for voip.
The documentation says,
"When you configure a stream for VoIP, the system takes over management of the underlying socket. If new data arrives, the system wakes up your applicationl".
This happens for me, only with that debugger stuff.
Not when its running standalone on the device.
I've been able to implement VoIP with multitasking, i.e., my application keeps running in the background, and notifies the user when there's an incoming call, using LocalNotifications.
The strange issue that I find is, this works only when I have my debugger running.
1. When I 'Build and Debug', with some breakpoints at the incoming voip call notification handlers in my app., it reaches there, and then goes on fine.
2. When I 'Build and Run' (disabled breakpoints), this point is not reached (I found out through the console logs).
Strangely, when I 'Enable' and then 'Disable' breakpoints, then the application is waken up by the system, and I get the notifications.
After this, notifications keep coming even in the background.
3. When I run the app stand-alone on the device, nothing works, but the application is not suspended, and when I switch back to my application, the notifications come.
I've tried this on all the beta releases, and the final GM release. Its the same.
I've done the voip and audio property setting in the plist and sockets configurations for voip.
The documentation says,
"When you configure a stream for VoIP, the system takes over management of the underlying socket. If new data arrives, the system wakes up your applicationl".
This happens for me, only with that debugger stuff.
Not when its running standalone on the device.
Any ideas.
I have also been trying to run voip on my iphone and I am running into some of the same issues. Any information on Business PBX or Voip Phones would be very helpful. Thanks in advance.
-Charlie
Last edited by charlieluc1968; 01-16-2012 at 07:54 PM.
I have also been trying to run voip on my iphone and I am running into some of the same issues. Any information would be very helpful. Thanks in advance.
-Charlie
It was my mistake in fact.
I tried to get voip running in background on good old iphone 3g.
It was jailbroken and patched to support background execution.
But it did not help - application did not wake up for incoming data anyway.
I suppose it is hardware limitation of iphone 3g.
New 3gs / 4 / 4s works good.
Check this document - it is the best article that I discovered. Loading