UI locked in unusable state after failed call

This app is ghastly. I don't think I have ever encountered a more unintuitive, buggy release of a product. No one should use it. Hard to navigate through and to its various functions, and it has not, after failing to reach a number in Germany that is out of order, it is locked in some sort of half screen more on my iPhone that makes it unusable. If you are thinking about using this version, don't.

Unfortunately, I can't. I got rid of it by deleting the app and downloading it again. The best I can do is describe it. Half the screen was black. The rest of the screen seemed to show the portion of the app that wasn't blacked out. Couldn't make anything work, however. After redownloading, it seems to be working OK.
It also seemed to be less intuitive than before. I had a hard time figuring out how to find my Skype credit info and to get to my contacts when trying to make a call. It seemed to want to try to make use the text messaging function. Maybe I've just learned where things are now because it seems easier to use. Annoying for awhile, though.

Similar Messages

Call remains in "conferenced" state after the call is released

We have a scenario where a lengthy recorded message is set up through a ICM call routing script. If we call the number we assigned to the script using our hard phones the call is disconnected as soon as the recorded message is finished playing.
When we use Cisco Administrator Desktop and the conference feature, the call remains in the "conferenced" state after the call has been released.
My assumption was that our reports would be smarter than CAD and would get it right. However, reporting agrees with CAD, it thinks the call remained on a conference call for the whole time.
In the script we set some variables for the call, play the message through "RunExtScript" node, set a call type, than use the "ReleaseCall" node to disconnect the call. Any ideas how we can configure the script other than this?

Hi,
can you tell us more - do you have Translation Routing set up, perhaps?
Also, can you take a look at the Router Log (on the Distributor server).
And please swith the script to Monitoring mode to see where it fails.
G.

FaceTime loud speaker pop out of iMac after failed call

Hi all,
I have been experiencing a wierd issue lately. I have been using facetime on my mac (Imac 27" 2009 model) to another buddy who has a brand new mac with facetime. We both have OSX lion and most times it works flawlessly. One nasty thing I have seen is if I try to call him and it fails, if he tries to call me back right away as the call comes in my imacs speakers start poping really loudly. Louder than the volume is set to.. I cant turn it off with the mute either... I end up having to quickly go into facetime and turn it off and then reboot to make it go away.. its really annoying and im afraid its going to hurt my speakers.. anyone else see this?

Also I copied this from my other computer web page:
Reported Phishing website ahead. Your network ha been monitored. Your network has been compromised due to Browser hijacking.The browser hijacking software may redirect you towards phishing websites that try to access your Login Password details. To fix this browser redirection issue we recommend you ask for instant help. Help Line 1 877 899 1824.
Then another smaller popup window pops up
http://www.pcassists.info
Security Error
Call Helpline 1877 899 1824
So this is what I was talking about, and the small popup window plus the larger Window stating "Reported Phishing website ahead" will not go away and I cannot use Safari anymore even after I shut down my computer, disconnected it, and then signed on again and reopened Safari, it still takes me to that page and I cannot get out of it.
PLEASE HELP!!!!!!!!

Slide to unlock after a failed call

When I have a call that fails for some reason and the phone is “locked” it returns to the locked state, with a “call failure” message. All fine.
However, when I later “slide to unlock” the phone (usually after I’ve finished my journey) the iPhone always immediately calls the failed caller back.
I think there is a similar effect with missed calls.
I find this automatic calling without a prompt very irritating. Is there some way to disable this?
Thanks for any info...

First, try to reset the phone by holding the sleep and home button for about 10sec, until the Apple logo comes back again. You will not lose data by resetting.
If this does not work, try to set it up as new device, explained here:
How to erase your iOS device and then set it up as a new device or restore it from backups
If still no luck, get it checke by Apple:
iPhone - Contact Support - Apple Support

When my iPhone 4S (with ios7) experiences a failed call while connected to my Bluetooth hands free in my car(screen locked) the failed call appears on the locked screen, as it should, then when I unlock the phone it automatically redials the failed call,

When my iPhone 4S (with ios7) experiences a failed call while connected to my Bluetooth hands free in my car(screen locked) the failed call appears on the locked screen, as it should, the problem arises whenever I unlock the phone, it automatically redials the last failed call, it doesn't do this with missed calls that are on the locked screen, if any. It is really annoying as sometimes the phone doesn't respond to attempts to end the call before it connects to the number. I then have to explain that it was my phone and not me, I look like an idiot, which I don't really need any extra help with!! Does anyone have any ideas? I don't want to stop missed call from showing in the locked screen but it might be associated with the failed calls and therefore be the only resolution

I have had the same issue which was driving me mad but think I have just found a way around it. In iOS 7 if you swipe up on the lock screen to access quick settings and go into timer then click the home button you get into the phone without calling the person back. Not a great 'fix' but hope it works for you. Come on Apple this isn't good enough, fix this bug otherwise you will lose your customers.

HT2527 iphone locked after receiving call

My iphone locked after receiving call. On screen only appears busy alert.

Hi tavaresjx,
If you haven't already done so, you may want to restart or reset the iPhone:
iPhone, iPad, iPod touch: Turning off and on (restarting) and resetting
http://support.apple.com/kb/HT1430
Restarting your iOS device
1. Press and hold the Sleep/Wake button for a few seconds until the red "slide to power off" slider appears, and then slide the slider.
2. After the device has turned off, press and hold the Sleep/Wake button until the Apple logo appears.
Resetting your device
If your device stops responding, you can reset it by pressing and holding both the Sleep/Wake and Home buttons for at least ten seconds, until the Apple logo appears.
If the above does not resolve your issue, the next best step will be to restore your iPhone using a computer with iTunes. Please be sure to backup your iPhone first.
Choosing an iOS backup method (Should I use iTunes or iCloud to back up my iOS device?)
http://support.apple.com/kb/HT5262
iTunes: Restoring iOS software
http://support.apple.com/kb/HT1414
Thanks,
Matt M.

How can I prevent oracle from locking accounts after failed logins?

how can I prevent oracle from locking accounts after failed logins?
Thanks

svarma wrote:
So what is the difference between the profile settings ...FAILED_LOGIN_ATTEMPTS and the parameter settings SEC_MAX_FAILED_LOGIN_ATTEMPTS?
Prior to 11g we only used profiles to control failed_login_attempts.. Then why we need thsi new parameter now?http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/initparams221.htm#I1010274
http://download.oracle.com/docs/cd/E11882_01/server.112/e17222/changes.htm#UPGRD12504
http://download.oracle.com/docs/cd/E11882_01/server.112/e17118/statements_6010.htm#SQLRF01310
As documented ...
FAILED_LOGIN_ATTEMPTS is a property of a profile, and will lock an account
SEC_MAX_FAILED_LOGIN_ATTEMPTS is an initialization parameter and will drop a connection but says nothing about locking accounts.

Why does Ipad lock after failing your RESTRICTION code

Why Does the ipad lock after failing your RESTRICTIONS passcode I mean what could possibly changing restrictions have to do with people doing stuff bad on you ipad why make it lock you from your ipad tell me why apple WHY

We are fellow users here on these user-to-user forums, you're not talking to iTunes Support nor Apple.
As far as I know Apple haven't said. What's your definition of 'bad stuff' ? Being able to disable restrictions can potentially unhide the App Store and/or iTunes store apps, and allow in-app purchases to be made - therefore allowing purchases to be made on your account.

N95 how to disable keypad lock after phone call

hi!
i dont know is this the issue with lates firmware v20, but i noticed somehing that is quite annoying.
after i recieve phone call, and if phone is locked, i open slider, talk, finish call, and then phona auomatically locks.
is there a way to make it stay unlocked. because if after call i want to check something in phone i need to slide it close, and then open again, witch is annoying.
thank you.
ps. same thing happens with bult in lock system, and with best keylocker application.
so i guess it is firmware feature (or maybe bug)

Check in your phone settings
Keypad autolock period—Select whether the keypad is
locked when your device has been idle for a certain period
of time.
Phone autolock period—To avoid unauthorized use, you
can set a time-out after which the device automatically
locks. A locked device cannot be used until the correct lock
code is entered. To turn off the autolock period, select
None.
See ‘Glossary of PIN and lock codes’, p. 117.

Employee Record Remains Locked for a While After BAPI_EMPLOYEE_DEQUEUE

Hi All,
I'm exposing the following BAPI's:
I'm calling the following functions (through the webservice) in the following sequence:
BAPI_EMPLOYEE_ENQUEUE
BAPI_PERSDATA_CHANGE
BAPI_EMPLOYEE_DEQUEUE
The ENQUEUE and CHANGE operations work fine, m running the dequeue bapi but the record remains locked after that.
(as seen by SM12), it adds one more entry, and the employee remains locked. So question now is u2013 how to successfully Dequeue it now ?
Here is a copy of entries as seen in SM12 after Enqueue, Change, and Dequeue:
800 MZZZZZB 13:Ǻ:31 E PLOGI 80001CP00010358 0 1
800 MZZZZZB 13:26:31 E PREL 80000001273############################## 1 1
800 MZZZZZB 13:27:07 E BUT000 8000000002083 0 1
Important: The entries disappear after a while, so there is a delay in DEQUEUE to take effect.
Is there any configuration/customization to make DEQUEUE happen immediately?

Hi ,
Try using commit work statement after deque FM., else use DEQUE_ALL FM.
This may helps,
thanks & regards,
Kiran

Restarting project from beginning after failing quiz

I have set up an exam at the end of my Captivate 7 project, but I am having trouble getting the performance that I need. I was hoping someone could give me some insight into achieving the performance I want.
I have been able to achieve the following:
-I am allowing the user 3 attempts to pass the quiz
-If they pass any of the attempts, the course is considered complete (and/or passed)
However, I have not been successful at getting this outcome:
If the user fails all 3 attempts, I need the course to be considered complete but failed
Our requirement is that if the user fails the quiz all 3 times, then they must retake the entire course. What I have experienced is that when the user exits after failing, when they try to retake the course, it will take them to the last bookmarked location of the current attempt (in my case, the page after the quiz results slide that lets the user know they failed). It is considering the course Incomplete (and therefore bookmarking to the end) rather than considering it Complete and Failed (and allowing them to repeat the course from a fresh start).
I have tried the following preferences with no luck:
Complete, Success/Completion Criteria: Slide views and/or quiz, with Quiz is passed or the quiz attempt limit is reached. This resulted in the user getting a "complete" status and certificate for the course, even if they failed all 3 times.
Passed/Failed, Success/Completion Criteria: Quiz is passed. This results in the course getting stuck in an Incomplete state after failure. When they exit they don't have the option to retake from the beginning and keep getting bookmarked to the last slide of the project.
Any ideas on how I can set the preferences? I was considering using the Project End Option of Looping the project, but I'm not sure how this will perform. Or maybe I need to use JavaScript to force this? We use SCORM 1.2 / Meridian LMS.
Thanks for considering,
Holly

Thanks Rod!
Your comments were very helpful. I think your advice on avoiding using Javascript to force the issue was a great tip.
Just as a follow up, I wanted to let you know what my team and I came up with upon further brainstorming. We ended up using some navigation and advanced actions to reset the course internally, without having to involve or upgrade the SCORM.
Here's the solution we are going with:
We allow the user infinite attempts at the exam (under preferences), but are using advanced actions to reset the course if the user fails three times in a row.
From the exam results page, when the user clicks the Continue button, the slide just after the results page has a conditional action that executes On Enter of the page. The action has 3 types of decisions - what happens if they pass, what happens if they fail, and what happens if they fail on an attempt that is a multiple of 3.
If the user passes the exam (if the variable cpQuizInfoTotalCorrectAnswers is greater or equal to 4), then it jumps them to a page letting them know they passed (and under preferences, the course is considered complete once they pass).
If the user fails the exam (cpQuizInfoTotalCorrectAnswers is less than 4), and it is not an attempt on a multiple of three (cpQuizInfoAttempts does not equal 3, does not equal 6, does not equal 9, and does not equal 12), then it jumps to a slide with a button we created called "Retake Exam." The button jumps them back to the introduction to the exam.
If the user fails the exam (cpQuizInfoTotalCorrectAnswers is less than 4), and it is their 3rd attempt, it jumps them to a page that has a "Restart Course" button. This button executes a big advanced action that jumps them to slide 1, resets any user variables to 0, and shows or hides and thing that became unlocked as the user progressed through the course the first time.
We set the actions up so that after 3, 6, 9, or 12 attempts, it will make take them to the "Restart Course" page, figuring by the 12th attempt they should have passed.
Just food for thought and wanted to share the solution.
Thanks for all your help!

CONC-SM TNS FAIL Call to PingProcess failed for IEMDPDEV

Concurrent manager internal log file showing error CONC-SM TNS FAIL Call to PingProcess failed for IEMDPDEV after application startup and showing status "System Hold or Fix Manager" in system administrator> administer. When ICM Fixed from administer Concurrent manager its start works and no error found in manager log file.
We have a RAC based environment and getting cold backup of application & database everyday after a shutdown of application and database.
This is our production environment we only face this issue in our production environment and no recent changes made or patch applied on environment.
Internal manager log file
Shutting down Internal Concurrent Manager : 13-OCT-2014 01:31:32
13-OCT-2014 01:31:32
The ICM has lost its database connection and is shutting down.
Spawning reviver process to restart the ICM when the database becomes available again.
Spawned reviver process 30597.
List of errors encountered:
_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-03114: not connected
to ORACLE
Review your error messages for the cause of the error. (=<POINTER>)
_ 2 _
Routine AFPSMG encountered an ORACLE error. ORA-03114: not connected
to ORACLE
Review your error messages for the cause of the error. (=<POINTER>)
_ 3 _
Routine FDPCRQ encountered an ORACLE error. ORA-03113: end-of-file on
communication channel
Review your error messages for the cause of the error. (=<POINTER>)
APP-FND-01388: Cannot read value for profile option FND_MGR_STRTUP_THRES_TIME in routine &ROUTINE.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The PROD_1004@PROD internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting PROD_1004@PROD Internal Concurrent Manager -- shell process ID 8210
          logfile=/u01/oracle/inst/apps/PROD_prodapps/logs/appl/conc/log/PROD_1004.mgr
          PRINTER=noprint
           mailto=oracle
          restart=N
             diag=N
            sleep=30
             pmon=4
           quesiz=1
          Reviver is ENABLED
+---------------------------------------------------------------------------+
Application Object Library: Concurrent Processing version 11.5
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
Internal Concurrent Manager started : 13-OCT-2014 08:02:25
+---------------------------------------------------------------------------+
                   Process monitor session started : 13-OCT-2014 08:02:25
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
13-OCT-2014 08:02:26 - Node:(PRODAPPS), Service Manager:(FNDSM_PRODAPPS_PROD) currently unreachable by TNS
                     Process monitor session ended : 13-OCT-2014 08:02:26
                   Process monitor session started : 13-OCT-2014 08:04:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:04:26
                   Process monitor session started : 13-OCT-2014 08:06:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:06:26
                   Process monitor session started : 13-OCT-2014 08:08:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:08:26
                   Process monitor session started : 13-OCT-2014 08:10:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:10:26
                   Process monitor session started : 13-OCT-2014 08:12:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:12:26
                   Process monitor session started : 13-OCT-2014 08:14:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:14:26
                   Process monitor session started : 13-OCT-2014 08:16:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:16:27
                   Process monitor session started : 13-OCT-2014 08:18:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:18:27
                   Process monitor session started : 13-OCT-2014 08:20:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:20:27
                   Process monitor session started : 13-OCT-2014 08:22:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:22:27
                   Process monitor session started : 13-OCT-2014 08:24:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:24:27
                   Process monitor session started : 13-OCT-2014 08:26:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:26:27
                   Process monitor session started : 13-OCT-2014 08:28:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:28:27
                   Process monitor session started : 13-OCT-2014 08:30:27
                     Process monitor session ended : 13-OCT-2014 08:30:28
                   Process monitor session started : 13-OCT-2014 08:32:28
                     Process monitor session ended : 13-OCT-2014 08:32:28
                   Process monitor session started : 13-OCT-2014 08:34:28
                     Process monitor session ended : 13-OCT-2014 08:34:28
                   Process monitor session started : 13-OCT-2014 08:36:28
                     Process monitor session ended : 13-OCT-2014 08:36:28
                   Process monitor session started : 13-OCT-2014 08:38:28
                     Process monitor session ended : 13-OCT-2014 08:38:28
                   Process monitor session started : 13-OCT-2014 08:40:28
                     Process monitor session ended : 13-OCT-2014 08:40:28
                   Process monitor session started : 13-OCT-2014 08:42:28
                     Process monitor session ended : 13-OCT-2014 08:42:28
                   Process monitor session started : 13-OCT-2014 08:44:28
                     Process monitor session ended : 13-OCT-2014 08:44:28
                   Process monitor session started : 13-OCT-2014 08:46:28
                     Process monitor session ended : 13-OCT-2014 08:46:28
                   Process monitor session started : 13-OCT-2014 08:48:28
                     Process monitor session ended : 13-OCT-2014 08:48:29
                   Process monitor session started : 13-OCT-2014 08:50:29
                     Process monitor session ended : 13-OCT-2014 08:50:29
                   Process monitor session started : 13-OCT-2014 08:52:29
                     Process monitor session ended : 13-OCT-2014 08:52:29
                   Process monitor session started : 13-OCT-2014 08:54:29
                     Process monitor session ended : 13-OCT-2014 08:54:29
                   Process monitor session started : 13-OCT-2014 08:56:29
                     Process monitor session ended : 13-OCT-2014 08:56:29
                   Process monitor session started : 13-OCT-2014 08:58:29
                     Process monitor session ended : 13-OCT-2014 08:58:29
                   Process monitor session started : 13-OCT-2014 09:00:29
                     Process monitor session ended : 13-OCT-2014 09:00:29
                   Process monitor session started : 13-OCT-2014 09:02:29
                     Process monitor session ended : 13-OCT-2014 09:02:29
                   Process monitor session started : 13-OCT-2014 09:04:29
                     Process monitor session ended : 13-OCT-2014 09:04:29
                   Process monitor session started : 13-OCT-2014 09:06:29
                     Process monitor session ended : 13-OCT-2014 09:06:30
                   Process monitor session started : 13-OCT-2014 09:08:30
                     Process monitor session ended : 13-OCT-2014 09:08:30
                   Process monitor session started : 13-OCT-2014 09:10:30
                     Process monitor session ended : 13-OCT-2014 09:10:30
                   Process monitor session started : 13-OCT-2014 09:12:30
                     Process monitor session ended : 13-OCT-2014 09:12:30
                   Process monitor session started : 13-OCT-2014 09:14:30
                     Process monitor session ended : 13-OCT-2014 09:14:30
                   Process monitor session started : 13-OCT-2014 09:16:30
                     Process monitor session ended : 13-OCT-2014 09:16:30
                   Process monitor session started : 13-OCT-2014 09:18:30
                     Process monitor session ended : 13-OCT-2014 09:18:30
                   Process monitor session started : 13-OCT-2014 09:20:30
                     Process monitor session ended : 13-OCT-2014 09:20:30
                   Process monitor session started : 13-OCT-2014 09:22:30
                     Process monitor session ended : 13-OCT-2014 09:22:30
                   Process monitor session started : 13-OCT-2014 09:24:30
                     Process monitor session ended : 13-OCT-2014 09:24:30
                   Process monitor session started : 13-OCT-2014 09:26:30
                     Process monitor session ended : 13-OCT-2014 09:26:30
                   Process monitor session started : 13-OCT-2014 09:28:30
                     Process monitor session ended : 13-OCT-2014 09:28:30
                   Process monitor session started : 13-OCT-2014 09:30:30
                     Process monitor session ended : 13-OCT-2014 09:30:31
                   Process monitor session started : 13-OCT-2014 09:32:31
                     Process monitor session ended : 13-OCT-2014 09:32:31
                   Process monitor session started : 13-OCT-2014 09:34:31
                     Process monitor session ended : 13-OCT-2014 09:34:31
                   Process monitor session started : 13-OCT-2014 09:36:31
                     Process monitor session ended : 13-OCT-2014 09:36:31
13-OCT-2014 09:38:31
Request : 1393181
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:31
Starting FNDCRM Concurrent Manager                 : 13-OCT-2014 09:38:31
                     Process monitor session ended : 13-OCT-2014 09:38:31
13-OCT-2014 09:38:31
Request : 1393182
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:31
Starting FNDCRM Concurrent Manager                 : 13-OCT-2014 09:38:31
Starting AMSDMIN Concurrent Manager                : 13-OCT-2014 09:38:31
                     Process monitor session ended : 13-OCT-2014 09:38:31
13-OCT-2014 09:38:31
Request : 1393183
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:31
Starting C_AQCT_SVC Concurrent Manager             : 13-OCT-2014 09:38:31
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393184
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:32
Starting DownloadProcessorMigrationMode Concurrent Manager : 13-OCT-2014 09:38:32
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393185
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:32
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393186
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:32
Found dead process: spid=(10691), cpid=(282513), ORA pid=(39), manager=(0/4)
Found dead process: spid=(10694), cpid=(282514), ORA pid=(40), manager=(0/4)
Starting FFTM Concurrent Manager                   : 13-OCT-2014 09:38:32
Starting FNDCRM Concurrent Manager                 : 13-OCT-2014 09:38:32
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393187
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:32
Starting FFTM Concurrent Manager                   : 13-OCT-2014 09:38:32
Starting FNDCPOPP Concurrent Manager               : 13-OCT-2014 09:38:32
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393188
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting FTE_TXN_MANAGER Concurrent Manager        : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393189
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting IEU_SH_CS Concurrent Manager              : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393190
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting IEU_WL_CS Concurrent Manager              : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393191
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting INVMGR Concurrent Manager                 : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393192
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting INVTMRPM Concurrent Manager               : 13-OCT-2014 09:38:33
Starting INVMGR Concurrent Manager                 : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393193
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting INVTMRPM Concurrent Manager               : 13-OCT-2014 09:38:33
Starting OAMCOLMGR Concurrent Manager              : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393194
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting OAMGCS_PRODAPPS Concurrent Manager        : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393195
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting PASMGR Concurrent Manager                 : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393196
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting PODAMGR Concurrent Manager                : 13-OCT-2014 09:38:34
Starting PASMGR Concurrent Manager                 : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393197
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting RCVOLTM Concurrent Manager                : 13-OCT-2014 09:38:34
Starting PODAMGR Concurrent Manager                : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393198
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting RCVOLTM Concurrent Manager                : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393199
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting WFALSNRSVC Concurrent Manager             : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
                     Process monitor session ended : 13-OCT-2014 09:38:35
13-OCT-2014 09:38:35
Request : 1393200
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:35
Starting WFMLRSVC Concurrent Manager               : 13-OCT-2014 09:38:35
                     Process monitor session ended : 13-OCT-2014 09:38:35
13-OCT-2014 09:38:35
Request : 1393201
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:35
Starting WFWSSVC Concurrent Manager                : 13-OCT-2014 09:38:35
                     Process monitor session ended : 13-OCT-2014 09:38:35
13-OCT-2014 09:38:35
Request : 1393202
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:35
Starting WMSTAMGR Concurrent Manager               : 13-OCT-2014 09:38:35
                     Process monitor session ended : 13-OCT-2014 09:38:35
                   Process monitor session started : 13-OCT-2014 09:40:05
                     Process monitor session ended : 13-OCT-2014 09:40:05
                   Process monitor session started : 13-OCT-2014 09:42:05
Regards
Usman

Below is the solution provide by the SR Team its works perfectly our enviorment.
Please perform the following steps:
1. Stop all middle tier services including the concurrent managers. Make sure no FNDLIBR, FNDSM, or other dead processes are running.
    (restart application and database OS (i have done this step additionally))
2. Stop and then restart the database.
3. Connect to SQLPLUS as APPS user and run the following :
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
4. Reference Note.260887.1 regarding the Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES.
5.. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and Web tiers to repopulate the required system tables.
6. Connect to SQLPLUS as APPS user and run the following statement :
select CONCURRENT_QUEUE_NAME
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME like 'FNDSM%';
If the above SQL does not return any value please do the following:
cd $FND_TOP/patch/115/sql
Connect to SQLPLUS as APPS user and run the following script :
SQL> @afdcm037.sql;
Reference Note 218893.1 How to Create The Service Manager 'FNDSM' on Oracle Applications
to create libraries for FNDSM and create managers for preexisting nodes.
Check again that FNDSM entries now exist:
select CONCURRENT_QUEUE_NAME
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME like 'FNDSM%';
7. Please run the Concurrent Manager Recovery feature to address any Concurrent Manager / Concurrent Processing issues within the Oracle Application Manager.
8. Start the middle tier services including your concurrent manager.
9. Retest the issue.
Regards
Usman

SPA112 FW bug confirmed: registration broken during and after outbound call

After receiving and configuring my new SPA112, everything seemed to work out just fine: registration to the SIP proxy, inbound calls, etc. However, at some point I discovered that outbound calls would typically only work for a certain amount of time, after which the connection to the callee would be lost, just like the my registration to the SIP proxy. In the SPA112's Web interface, the device reports "Registration State: Failed" in such cases. Only a reboot of the device will result in a successful registration again. Firmware version: 1.3.5(004).
To diagnose the problem, I enabled both syslog and debug logging and started capturing and analyzing what is going wrong:
[Before call]
SIP.REGISTER
SIP.TRYING
SIP.UNAUTHORIZED (with nonce)
SIP.REGISTER
SIP.TRYING
SIP.OK
Also the debug logging reports "LOCAL3.DEBUG: [0]RegOK. NextReg in X".
So far, so good.
[During/after call]
We see two (periodic) registration sequences:
SIP.REGISTER
SIP.TRYING
SIP.UNAUTHORIZED (with nonce)
LOCAL3.DEBUG: SIP_tsClientEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
LOCAL3.DEBUG: SIP_tsClientEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
LOCAL3.DEBUG: SIP_tsCreateClient()
SIP.REGISTER
SIP.TRYING
LOCAL3.DEBUG: SIP_tsClientEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
SIP.OK
LOCAL3.DEBUG: SIP_tsClientEventProc(event: 28)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 28)
LOCAL3.DEBUG: [0]RegOK. NextReg in X
Which is OK and the same as before the call. This one is however shortly followed by the following (second registration sequence of) debug messages:
LOCAL3.DEBUG: SIP_tsClientEventProc(event: 4)
LOCAL3.DEBUG: tryAltIp_delay()
LOCAL3.DEBUG: RSE_DEBUG: getting alternate from domain:<proxy>
LOCAL3.DEBUG: SIP_regTsEventProc(event: 4)
LOCAL3.DEBUG: SIP_regTsEventProc(event: 32)
LOCAL3.DEBUG: 2. RSE:GetServerAddrErr(<proxy>,0)=-101
LOCAL3.DEBUG: SIP_tsCreateClient(), 1781, uiTmrF=1600, SIP_TMR_F_INIT=1600
LOCAL3.DEBUG: [0]Reg Addr Change(0) 29dfc552:5060->0:5060
LOCAL3.DEBUG: tpError at [SIP_tsCreateClient:1817]
These two registration sequences (regular SIP messages at the one hand and the debug messages at the other hand) are alternating, and the succesfull registration is followed by the failing registration in a short time, so most typical state is "Failed".
Any suggestion on what I could try to solve the issue is welcome!

I'm able to reproduce the problem in my test lab.
It seems that device can't fetch IP address of the SIP proxy from it's internal cache during active call (GetServerAddrErr error -101). And the issue doesn't solve in full even after the calls end.
It is not networking issue between device and DNS server as no DNS query has been issued (the IP address is cached from previous query that has been responded successfully).
As a workaround I configured proxy IP instead of name.
It work.
It seems we hit (another) firmware bug.

How we can chcek reason of failed calls over PGW or MGW

Dear All
We are using PGW 2200 in Signalling mode with AS5400 as MGW to terminate call over TDM/PSTN. Can anybody let me know how we can check "why attempted call failed or reason of failed call from MGW level or PGW level.
Here one thing i want to know we are not using any RADIUS server for log or billing. Please tell me how wecan chcek why & where call faield on MGW or PGW or far end operator side with reason.i chcked few document but no comnads i found to check failed reason of attempted calls..
Please help me with this info.
Thanks
Amit--. .

First of all you have to check C7 link state and CICs state
1. Enter to PGW host with username mgcusr
2 Run mml
3 Check active platform by command rtrv-ne
4 Check C7 link rtrv-c7lnk:all
All C7 links must be in service: IS
5 Check CIC rtrv-tc:carrier10ss7svc1
All CICs must be in Idle state
If it is so then we can go to next steps.
The best way to check reason of failed calls is to use the snooper utility.
Login as root
change directory to
/opt/CiscoMGC/bin
run utility
./snooper int bge0 ss7 itu 1-234-5 detail
Where 1-234-5 - DPC of your carrier
After that you will see a flood of ISUP messages.
In REL message you can find the reason why your call attempt was failed.
on MGW (if it is Cisco AS5xxx) you can run
debug isdn q931 command on all trunks or on selected Dchannel: debug isdn q931 interface Dchannel x/x
You will get isdn messages. In Disconnect message you can find the reason why your call attempt was failed.Good luck!

Up Date stat is failing

Dear All
DB Update stat is failing please help
BR0280I BRCONNECT time stamp: 2011-11-12 23.46.15
BR0884I Statistics collected for table: SAPDAT./BIC/0CZE_Q04, rows old/new: -1/13
BR0280I BRCONNECT time stamp: 2011-11-12 23.46.15
BR0881I Collecting statistics for table SAPDAT./BIC/B0000002000 with method/sample E/P.300 ...
BR0280I BRCONNECT time stamp: 2011-11-13 01.34.04
BR0301E SQL error -3113 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPDAT"', TABNAME => '"/BIC/B0000002000"', ESTIMATE_PERCENT => 0.300, METHOD_
ORA-03113: end-of-file on communication channel
BR0280I BRCONNECT time stamp: 2011-11-13 01.34.04
BR0261E BRCONNECT cancelled by signal 13
BR0280I BRCONNECT time stamp: 2011-11-13 01.34.04
BR0301E SQL error -1092 at location db_connect-2,SQL statement:
'CONNECT /'
ORA-01092: ORACLE instance terminated. Disconnection forced
BR0310E Connect to database instance EBP failed
BR0806I End of BRCONNECT processing: cehfacda.sta2011-11-13 01.34.04
BR0280I BRCONNECT time stamp: 2011-11-13 01.34.04
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 5
Thanks
Reddy

Hi,
My system is already on 10.2.0.4.0 and in sm21 i could find this log
Documentation for system log message BY 2 :
After the attempt to call a database operation, the database system has
returned the error code specified in the message, which indicates that
the operation concerned could not be executed successfully.
61446 354420 h Database Error (Non-SQL) BY 2 3113 FET dbds 596
Thanks
Reddy

UI locked in unusable state after failed call

Similar Messages

Maybe you are looking for