Wonder if anyone knows the secret FreeSWITCH magic to get FusionPBX to ignore a 488 Not Acceptable Here error message from a single registered device (in this case a PUSH server) from breaking the entire call? I've included a diagram of what's happening to the call.
Normally, the Push Service is sat there, happily registered and waiting to wakeup the application via Apple or Googles notification methods and the call completes no problem.
However we have an issue when the application is open, so the PUSH service responds with 'Go away, the app is open already' and just lets the awake app deal with the INVITE. The deskphone and the app both receive the call, but FusionPBX has terminated the call almost immediately tears it down resulting in a missed call.
So, my question is.... is there anyway to override this behaviour so that it doesn't tear down the call if one of the endpoints returns this error code? Any ideas welcome.
Normally, the Push Service is sat there, happily registered and waiting to wakeup the application via Apple or Googles notification methods and the call completes no problem.
However we have an issue when the application is open, so the PUSH service responds with 'Go away, the app is open already' and just lets the awake app deal with the INVITE. The deskphone and the app both receive the call, but FusionPBX has terminated the call almost immediately tears it down resulting in a missed call.
So, my question is.... is there anyway to override this behaviour so that it doesn't tear down the call if one of the endpoints returns this error code? Any ideas welcome.
