No sountd notifications on device

Hello,
I have lost all sound notifications on my device, incoming calls, texts, alarm, etc.
Have tried turning on and off and battery pull. Nothing seems to work.
Have had this issue in the past but a restart of device has always fixed it in the past.
Thanks

Are you sure you don't have any other programs installed which can block this? I'd suggest removing all 3rd party products from your BlackBerry

Similar Messages

Unity Connection 8.5 Outcall notification to device too agressive?

I’ve noticed the Unity Connection 8.5 outcall notification is too aggressive. Is there a way to change the outcall parameters to wait x minutes between redials?
For example Connection called my cell phone, while I am inputting my PIN I get a second call from Connection alerting me to new messages. While I’m listening to the messages I get a third call from Connection. I noticed same problem if device is my desk 7962 phone.
Unity Connection 8x Administration Guide
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/administration/guide/8xcucsagpdf.pdf

Hi Jason,
These timers can be changed via the User or User Template pages
User Templates New Notification Device
Revised November 16, 2010
Table 3-21 User Template New Notification Device Page
Field Description
Notification Device Type
Select a type of notification device from the list.
Display Name
Enter a descriptive name for the notification device.
Phone Number
(Applicable only to phone and pager notification devices.) Enter the phone number, including trunk access code, of the selected device. Use digits 0 through 9 and the following dialing characters in the phone number:
•, (comma) to insert a one-second pause.
•# and * to correspond to the # and * keys on the phone.
Users can change this number by phone.
Extra Digits
(Applicable only to phone and pager notification devices.) Enter any extra digits that Cisco Unity Connection dials after the phone number. The effect of the extra digits depends on the selected device. For pagers, the extra digits are shown on the pager display.
For example, the extra digits could be used to include a callback number when sending notifications to numeric pager devices. Extra digits can also be used to reach an extension, where the notification is configured to dial a public 800 access number and the extra digits would be sent at the opening greeting in order to reach the target extension.
Duration to Wait Before Dialing Extra Digits
(Applicable only to phone and pager notification devices.) Cisco Unity Connection can wait a specified number of seconds before dialing the digits in Extra Digits. Use this option if the automatic call progress detection is not reliable (for example, when phone lines are noisy or when ringing patterns are unusual).
Rings to Wait
(Applicable only to phone and pager notification devices.) Enter the number of times that Cisco Unity Connection allows the user phone to ring before ending the attempt. The setting must be at least 3 rings. Enter a higher number to give a user more time to get to the phone.
Default setting: 4 rings.
Busy Retry Limit
(Applicable only to phone and pager notification devices.) Indicates the number of times that Cisco Unity Connection tries to reach a user number that is busy. Select a higher number to reach someone who uses the phone frequently.
Default setting: 4 times.
Busy Retry Interval
(Applicable only to phone and pager notification devices.) Indicates the number of minutes that Cisco Unity Connection waits between attempts to reach a user number that is busy. Select a higher number to reach someone who has long phone conversations.
Default setting: 5 minutes.
RNA Retry Limit
(Applicable only to phone and pager notification devices.) Indicates the number of times that Cisco Unity Connection tries to reach a user who does not answer the phone. Select a higher number to reach someone who steps away from the phone briefly. Select a lower number to avoid disturbing others.
Default setting: 4 times.
RNA Retry Interval
(Applicable only to phone and pager notification devices.) Indicates the number of minutes that Cisco Unity Connection waits between attempts to reach a user who does not answer the phone. Select a higher number to reach a user who is away from the phone for long periods of time.
Default setting: 15 minutes.
Retries After Successful Attempt
(Applicable only to pager notification devices.) Indicates the number of times that Cisco Unity Connection calls the pager device after the first successful call to the device while the message that triggered the notification is still marked new. Use this setting in conjunction with the Retry Interval After Successful Attempt setting if users need additional reminders of new messages, or if users sometimes do not receive notifications even though the first call to the pager is successful.
If set to a value greater than 0 (zero), Connection makes periodic calls based on the Retry Interval After Successful Attempt until the user checks the message or the retry limit is reached. For example, if Retries After Successful Attempt is set to 2 and Retry Interval After Successful Attempt is set to 15, and the user receives a new message at noon, Connection will call the pager device at noon. If that call is answered, but the user does not check the message before 12:15 pm, Connection calls the pager device again at 12:15 pm. If the user does not check the message before 12:30 pm, Connection calls the pager device a second time at 12:30 pm.
Note This setting generates a series of notifications that is separate from the series that is generated if you enable the Repeat Notification If There Are Still New Messages setting on the Edit Notification Device page. To avoid confusing the user with multiple repeating notifications, we recommend that you use either the Retries After Successful Attempt setting or the Repeat Notification If There Are Still New Messages setting, but not both.
Enter a value between 0 and 100. A value of 0 (zero) means that Connection does not retry the notification after the first successful call to the pager.
Default setting: 0.
Retry Interval After Successful Attempt
(Applicable only to pager notification devices.) Indicates the interval at which Cisco Unity Connection retries calling the pager device after the first successful call to the device if Retries After Successful Attempt is set to a value greater than 0 (zero) and the user has not yet checked the message. Use this setting in conjunction with the Retries After Successful Attempt setting if users need additional reminders of new messages, or if users sometimes do not receive notifications even though the first call to the pager is successful.
Enter a value between 0 and 100 minutes. A value of 0 (zero) means that Connection makes additional retries as soon as a port is available to dial the device.
Default setting: 1 minute.
Phone System
(Applicable to phone and pager notification devices only.) Select the phone system that the notification device uses.
Prompt for User ID on Notifications
(Applicable only to phone notification devices.) Indicate whether Cisco Unity Connection should prompt the user to enter a user ID. The user is always asked for a PIN. Users may prefer not to enter a user ID in order to shorten the time that it takes to sign in.
Note Use this setting with caution and only if the phone is never answered by anyone other than the user.
SMPP Provider
(Applicable only to SMS notification devices.) Select the applicable SMPP provider.
To
(Applicable only to SMTP and SMS notification devices.) Depending on whether you are setting up message notification for a text-compatible mobile phone or pager, or for SMS (SMPP) devices:
•For SMTP text message notifications, enter the email address of the user text pager, text-compatible mobile phone, or another email account (such as a home email address).
•For SMS (SMPP) text message notifications, enter the phone number of the SMS-compatible device. The format and the number that you enter depends on the SMPP Provider. The provider may require that you include international country codes, beginning with a plus sign and followed by the country code, area, city, or trunk code, and then the number for the device (for example, +12065551234). Do not start with a zero or the international dialing prefix. Do not include spaces, dashes, parentheses or other punctuation.
Up to 128 characters can be entered in this field.
From
(Applicable only to SMTP and SMS notification devices.) For text-compatible mobile phones or pagers, enter the phone number that the user calls to check messages, or enter alphanumeric text (as applicable) in this field. The From phone number appears in the last line of any SMTP notification. A user can press the Return Call button on many text-compatible mobile phones to dial the phone number. The mobile phone must support automatic callback in order to use this feature.
For SMS (SMPP) devices, what you enter in this field depends on the SMPP Provider:
•If the SMPP Provider requires a "source address" for the server sending the message, enter the IP address for the Cisco Unity Connection server.
•If the SMPP Provider does not require a "source address," enter the number that the user calls to check messages. The format and the number that you enter depends on the SMPP Provider. The provider may require that you include international country codes, beginning with a plus sign and followed by the country code, area, city, or trunk code, and then the number for the device (for example, +12065551234). Do not start with a zero or the international dialing prefix. Do not include spaces, dashes, parentheses or other punctuation.
Note Consider that some SMPP Providers replace the number that you enter in the From field with their own phone number. For an alternative method of including a call back number, try entering the number that the user calls to check messages in the Message Text field.
Up to 40 characters can be entered in this field.
Message Header
(Applicable only to SMTP notification devices.) Enter any text you want Connection to put into the header of the notification message. For example, you might enter a legal disclaimer that you want to be sent with every notification message.
Message Text
(Applicable only to SMTP and SMS notification devices.) Enter the text message that the user wants to receive in a text notification. For example, you might enter "Urgent message for Technical Support" for a user who is on call for the technical support department. Every time a message arrives that matches the criteria selected in the message notification settings, Cisco Unity Connection sends the text you enter here.
Note To include a call back number, try entering the number that the user calls to check messages within the message text (for example, enter the number in this format: tel:2065551212).
Up to 160 characters can be entered in this field. (For SMS devices, depending on the character set you configure Connection to use, it is possible that messages that are shorter than 160 characters may be truncated.)
Message Footer
(Applicable only to SMTP notification devices.) Enter any text you want Connection to put into the footer of the notification message. For example, you might enter a legal disclaimer that you want to be sent with every notification message.
Include Message Information in Message Text
(Applicable only to SMTP and SMS notification devices.) Check this check box to include information about the new message in the text string that is sent to the notification device. This information can include caller name and caller ID (if available); the type of message (voice, email, fax); the time that the message was received; and, if the message was marked private or urgent, an indication of this status.
Include Message Count in Message Text
(Applicable only to SMTP and SMS notification devices.) Check this check box if you want the notification to include a count of the number of new messages in the mailbox.
Include a Link to Cisco PCA in Message Text
(Applicable only to SMTP notification devices.) Check this check box to include a link to the Cisco Personal Communications Assistant in the text string that is sent to the SMTP notification device.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/gui_reference/guide/8xcucgrg030.html#wp1082329
Cheers!
Rob

WinUSB notification of device reset

Hi,
I'm using MFC and WinUSB to develop an application to communicate with a USB device using a custom device class. I need the desktop application to be able to respond to device resets caused by a watchdog timer. During normal operation the application continuously
polls the device using WinUsb_ReadPipe(), when this returns false following a device reset, I disconnect the device, wait and then re-connect. The current process is working fine for re-connecting to the device, but about 40% of the time WinUSB_ReadPipe()
is reading spurious data before returning false and triggering re-connection to the device.
Is there a way for the USB hub to notify the application that it has detected a device reset that would enable me to immediately disconnect the device and avoid calling WinUsb_ReadPipe() after the device reset?
Thanks,
Mark

typically a device reset manifests itself as the device falling off of the bus and then reenumerating. If that is the case here a better solution is to register for file handle notifications and you will be told when it falls off.
d -- This posting is provided "AS IS" with no warranties, and confers no rights.

Can iTunes give audio notification when device sync finishes?

I'd like to get audio feedback when my device sync completes. So far, I haven't found any setting in Mavericks setting or in iTunes settings to do configure it to make a sound when it finished syncing.
Is there something that I missed, or is it impossible?

There is currently no option to set that would provide a sound when the sync is complete. You can send you suggestion to Apple, however:
Apple - Feedback
Cheers,
GB

QuickTime: How to get hot unplugged device notification

Hi,
I am using QuickTime to write a simple video capture application (from USB devices, FireWire). I have written to capture the video using SequenceGrabber and it works fine. I need to notify the user when video device being captured it hot unplugged. I can not find a way where I can receive notification from device when video device is hot unplugged. I have searched everywhere but I could not found anything useful. It seems that IOKit can be used to bind to attached devices and receive notification but I want to receive notification from QuickTime(SequenceGrabber or VideoDigitizer) instead of directly hooking to hardware.
Please someone help me.

Thanks for your reply. I have already checked the QuickTime documentation but I did not find how to detect when a video device is unplugged while in use. I got how to detect audio device removal by adding property listener and waiting for kQTSGAudioPropertyID_DeviceAlive notification.
But I can not find any such method for video device. I searched everywhere on google but could not find anything.

Syncing Mail Notifications Between Mac and iPhone

Hi
I been having this problem with the mail notifications not syncing between the Mail.app on my MacBook Pro and iPhone. Let me explain:
When I get a new email, I hear the sound and see the red notification icon appear on both the MacBook and the iphone. When it comes to checking the new email, here are the two possible scenarios:
a) If I check the new email on my phone, the red notification icon disappears from BOTH the iphone and the MacBook.
b) If I check the new email on my MacBook, the red notification disappears from the MacBook but DOESN'T disappears from the iPhone (that is until I open the app). This happens with both cases, when the app is "running" in the background or when it is complety closed.
I don't know if I am crazy but I am pretty sure that both of the notifications used to disappear before, no matter where I checked the mail.
I tried deleting and creating the email again on my phone, and it didn't work.
Here some info that could help find a solution:
- I'm using icloud email (@me.com)
MacBook
-Mountain Lion
iPhone:
- iOS 6 (this problem started before the upgrade)
- Push is on.
- Fetch (that suppodselly would be used only if push is off) is set to Manually.
- On the "Advanced" sub-menu inside the Mail settings, Push is also selected.
Hopefully this can actually be fix and I can prove myself that I was not crazy!!
Thanks in advance for the help!!

Anyone find a fix for this problem? I've been waiting for this since notification syncing was announced a couple years ago with iOS 6. I use iCloud for my email and find it very frustrating that when I read an email on my Mac or on iCoud.com that it doesn't automatically dismiss the notifications for those emails on my iOS devices until I open the mail app on each iOS device. Notification syncing works great with other apps. With iMessages, for example, when I read a message on my Mac running Yosemite, the notifications disappear on my iOS devices without opening the messages app (badge app icon, home screen notifications and notification center). Why can't they figure this out with email? I remember at my old job, I had an exchange account that properly synced mail notifications between devices, but it has never worked with my iCloud email. I wonder if I am just missing a particular setting or if Apple just blew it here. Any info would be greatly appreciated.

Gmail push and twitter/facebook notifications not working since ios 5

I have not been getting any push email notifications, the device does not seem to be receiving any mail unless I fetch it manually or wait for the 15 min fetch schedual. Also, I am not getting any of the integrated twitter notifications. Any possible fix?

Hi mr_black,
If you are having issues with notifications after updating to iOS7, you may find the following article helpful:
iOS: Understanding notifications
http://support.apple.com/kb/HT3576
Regards,
- Brenden

Error during the creation of notification

Dear All,
We are facing the error when we are carrying out the transaction EG90
for collective creation of notification for device replacement say out of 1000 equipments 998 notifications were created automatically but for rest two device locations the follwing error comes "internal error during determination of pm plant for device with equipment number xyz
error message EG621 .
I have cheked the master data of the equipments all maintended properly
can you give me some idea what coulld be the problem .
Regards
chan

There are quite a few OSS Messages for TCode EG90.
See if any of them are suitable.
PeteA

Cdemu issues (again), this time with KDE Device Notifier

OK, so I'm having trouble with cdemu again. This time it's not about mounting an image, but getting rid of it
Essentially, when I load an image with the cdemu client, KDE Device Notifier immediately recognises it as an inserted optical media... which is cool.
However, when I try to unload it with cdemu, it stays "stuck" in KDE Device Notifier, and I can't access any other image which I mount via cdemu afterwards.
In other words, I do the following...
cdemu load 0 <name>.iso
The image appears to be successfully loaded, and I can access it's contents with no trouble at all. KDE Device Notifier sees it normally, can mount it and open it in Dolphin.
Then, when I'm done with it, I do the following...
cdemu unload 0
This apparently unloads the image, as I can't open it in Dolphin anymore (or any other application within KDE), but KDE Device Notifier still sees it as if the "optical drive" is inserted, and it won't go away. If I try loading another image in cdemu, KDE will still see the previous one, and I won't be able to do anything with it.
I cannot mount or unmount it, I cannot open it in Dolphin or any other application (obviously, because the image isn't mounted anymore), but KDE Device Notifier still insists that it's there, and won't let me access any other image mounted via cdemu.
Since I have very little experience with cdemu and KDE's logs, I don't know what else I should post here, or where to find it...
Any advice or idea would be much appreciated. TIA!

Today the issue disappeared!
I don't understand, yesterday I spent my whole afternoon trying to find why it was not recognised, I rebooted a few times without any luck. In the evening I still had a cdemu iso mounted and left my laptop in "suspend to ram" state, and this morning as soon as I wake from suspend to ram I have a notification from device notifier that my iso is available! I tried to unmount / mount and reboot then mount / unmount, it now works fine...
So it seems the issue fixed itself... Don't know how though..
And the new version of kde-cdemu-manager works fine as well.

The device "EHCI Root Hub Simulation" @ 0xfd000000 has caused an overcurren

I Have the problem with my usb port
When My Mac reboot the system in the log read this message
USB Notification: The device "EHCI Root Hub Simulation" @ 0xfd000000 has caused an overcurrent condition. The hub it is attached to has been disabled
I can disable this message because the USB Port work correctly

Can you tell which USB is missing in System Profiler>Hardware?USB?
Are all USB devices unplugged?
Have you tried Resetting MacBook and MacBook Pro System Management Controller (SMC)...
http://docs.info.apple.com/article.html?artnum=303319

CUOM 2.3 sends multiple notifications for Event StoppedGSUPerformancePolling with same time stamps

Hi Alll,
I have a CUOM Version 2.3 which shows mutiple notifications per Device for Event StoppedGSUPerformancePolling with same time stamps. The message below is generated from the default All_Events for all devices.
Does anyone have a solution for that.
Regards Michael
This message is generated 8 times with the same time stamp in all messages.
** This message is generated from Cisco Unified Operations Manager **
ALERT ID                = 00012OW
CREATION TIME           = Sat 30-Oct-2010 16:31:57 CEST
MODIFIED TIME           = Sat 30-Oct-2010 17:00:58 CEST
STATUS                  = Active
SEVERITY                = Critical
MANAGED OBJECT          = 183.201.141.193
MANAGED OBJECT TYPE     = VoiceGateway
ASSOCIATED EVENTS       =
    Cleared:183.201.141.193:Unresponsive
    Active:183.201.141.193:StoppedGsuPerformancePolling
CUSTOMER IDENTIFICATION = Voice Port
CUSTOMER REVISION       = Voice Port

if you get SNMP timeout on multiple devices then the fault usually lies in the path that the polling follows to get to these devices and back to the server.
The problem obviously lies in the part path they have in common.
It is not unusual to see the highest backbone loads during the night, due to backups being taken.
Make sure the most important inter-switch links have no errors.
I would rather fix this then turn off alerting.
Cheers,
Michel

Alert and notification question

We are running LMS 3.1. Notification services are configured under DFM. We do receive alerts with event occurance, but don't get notification when device come back to normal state per event code. Any help will be appreciated.
Thanks,
Mohammad.

This probably has to do with how you have configured your notification group. Make sure you have both active and cleared checked as well as both critical and informational. The informational severity is required because cleared events/alerts are informational even though the event/alert they describe may have been critical.

Device Media Processor is busy

I just recently purchased a new torch 9850 and have only had it some six days. Overall its been working wonderfully so far whoever after a while the music player portion of the phone becomes unresponsive in playing a song with the notification of Device Media Processor is Busy. Thing is there isn't anything else playing whenever this comes about. Now I've been able to temporarily get rid of the problem by removing the battery while the phone is still on and performing a cold boot. Thing is I've had to do this 3 times now, so its starting to get rather annoying particularly for the fact I shouldn't have to do this or be experiencing this problem at all. Any ideas of what I should do would be greatly appreciated.

AmunRa wrote:
I just recently purchased a new torch 9850 and have only had it some six days. Overall its been working wonderfully so far whoever after a while the music player portion of the phone becomes unresponsive in playing a song with the notification of Device Media Processor is Busy. Thing is there isn't anything else playing whenever this comes about. Now I've been able to temporarily get rid of the problem by removing the battery while the phone is still on and performing a cold boot. Thing is I've had to do this 3 times now, so its starting to get rather annoying particularly for the fact I shouldn't have to do this or be experiencing this problem at all. Any ideas of what I should do would be greatly appreciated.
Hi AmunRa,
Reload your OS. Read this article.
How to perform a clean reload of the BlackBerry Device Software for Windows
Good luck!
Please thank those who help you by clicking the button.
If your issue has been solved, please resolve it by marking "Accept as Solution"

SCOM 2012 SP1 failed to send notifications by IM Channel

Hello, I have a problem with my SCOM 2012 SP1. When it tries to send notification by IM Channel I get the following alert in SCOM:
Notification subsystem failed to send notification using
device/server 'live.august.ru:5060' over 'sip' protocol to
'sip:[email protected]'.
Microsoft.Rtc.Signaling.OperationFailureException: The GetInbandDataAsyncResult
operation has failed with message: "The data session subscription to server
failed.". See the InnerException and FailureReason properties as well as the
logs for additional information. . Rule id:
Subscription077dc311_59c0_4ba5_a432_072b486cd287
At the same time the following event in the Application Event Log generates on the server with IM service:
Event Type: Warning
Event Source: Live Communications Server Authentication
Event Category: (1003)
Event ID: 16435
User: N/A
Computer: LCS
Description:
At least one invalid authentication signature was detected.
There were 2 messages with invalid signatures in the last 7112 minutes. The last one had the FROM header: sip:[email protected]
Cause: This could be due to a client or server which is not handling authentication correctly, or it could be due to an attacker.
Resolution:
None needed unless the failure count is high (>100). Check your network for any rogue clients. Restart the server if problem persists.
Notifications sent by the SMTP channel work fine!
I Have the following Servers:
LCS (live.august.ru) - Win 2003 EE SP2 + Live Communication Server 2005 SP1
SCOM - Win 2012 + SCOM 2012 SP1
Also I have a third server (Win 2003 + SCOM 2007 R2) and it sends notifications to the same VMLCS server successfully. The configurations of IM Channels are identical on both servers:
IM server: live.august.ru
Return address: sip:[email protected]
Protocol option: TCP
Authentication method: Kerberos
IM port: 5060
I tried to change the Authentication method to NTLM, and the port to 5061, but it doesn't help...

Hi,
Please refer to these following articles to configure IM channel correctly:
How to Create and Configure the Notification Action Account
http://technet.microsoft.com/en-us/library/hh212835.aspx
How to Enable an Instant Message Notification Channel
http://technet.microsoft.com/en-us/library/hh212690.aspx
Enabling Instant Messaging Notifications in System Center 2012 Operations Manager
http://opsmgrunleashed.wordpress.com/2012/02/24/enabling-instant-messaging-notifications-in-system-center-2012-operations-manager/
Alex Zhao
TechNet Community Support

Push Notification in Android using SMP 2.3

Dear All,
Please let me know the steps to configure push notification for working OData android project.
Thanks
Suresh

Hi Jitendra Kansal
Thanks for the document, we followed the document for IOS,
Device token was successfully generated and IOS device is successfully registered with SMP server.
After we execute the URL using REST CLIENT PLUG IN - POST method.
We can see following log in SMP server logs. We didn't receive any notification on device.
Please guide us where are we missing?.
2014-03-04 18:40:07.451 ERROR PUSH pool-10-thread-36 [com.sybase.sup.components.notification.apns.ApnsNotificationdelegate]Notification to [B@5b24b66b failed!
2014-03-04 18:39:03.442 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.util.PushDomainLogUtil]Domain logger is not enabled
2014-03-04 18:39:03.442 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.util.PushDomainLogUtil]log bucket set as PUSH default
2014-03-04 18:39:03.442 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.util.PushDomainLogUtil]logContext is not null
2014-03-04 18:39:03.442 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.util.PushDomainLogUtil]Logging for domain default
2014-03-04 18:39:03.442 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.util.PushDomainLogUtil]Inside Domain Logger for PushNotification. writeDomainLogs() called
2014-03-04 18:39:03.442 INFO PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.APNSNotificationProcessor]###### Push from Notnoop complete...
2014-03-04 18:37:58.446 INFO MMS Thread-256 [com.sybase.sup.jmo.notification.MessagingQueueNotificationProcessor]Number of batched messaging notifications processed 1
2014-03-04 18:37:58.445 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.apns.ApnsServiceFactory]Returning service from map...
2014-03-04 18:37:58.445 INFO PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.APNSNotificationProcessor]Device token - xxxxxxxxxxxxxxxxxxxxxxXXXXXXXXXX "token generated by system but manipulated here for posting....
2014-03-04 18:37:58.445 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.APNSNotificationProcessor]Push payload - {"aps":{"sound":"default","alert":"test","badge":2}}
2014-03-04 18:37:58.445 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.APNSNotificationProcessor]Sound : default
2014-03-04 18:37:58.445 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.APNSNotificationProcessor]Badge : 2
2014-03-04 18:37:58.445 WARN PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.APNSNotificationProcessor]Not a json object...
2014-03-04 18:37:58.445 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.APNSNotificationProcessor]Alert : test
2014-03-04 18:37:58.445 INFO PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.APNSNotificationProcessor]###### APNSNotificationProcessor processing notification...
2014-03-04 18:37:58.445 DEBUG PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.Notificationhandler]Processing notification
2014-03-04 18:37:58.445 INFO PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.Notificationhandler]APNSNotificationProcessor called
2014-03-04 18:37:58.445 INFO PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.Notificationhandler]notification type is APNS
2014-03-04 18:37:58.445 INFO PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.Notificationhandler]Inside ProcessNotification method
2014-03-04 18:37:58.445 INFO PUSH hz._hzInstance_2_mobdev1_push.cached.thread-64 [com.sybase.sup.components.notification.Notificationhandler]Inside call() method of Notificationhandler
2014-03-04 18:37:58.442 INFO PUSH Thread-256 [com.sybase.sup.components.notification.PushNotificationServiceImpl]Notification submitted to executor service
2014-03-04 18:37:58.441 DEBUG PUSH Thread-256 [com.sybase.sup.components.notification.Notificationhandler]Notificationhandler : domain logs are set
2014-03-04 18:37:58.441 DEBUG PUSH Thread-256 [com.sybase.sup.components.notification.Notificationhandler]apns notification
2014-03-04 18:37:58.441 INFO PUSH Thread-256 [com.sybase.sup.components.notification.Notificationhandler]Notificationhandler constructor is called
2014-03-04 18:37:58.441 INFO MMS Thread-256 [com.sybase.sup.jmo.notification.MessagingQueueNotificationProcessor]Submitting notification for DeviceName our device name with application id
2014-03-04 18:37:58.437 INFO MMS Thread-256 [com.sybase.sup.jmo.notification.MessagingQueueNotificationProcessor]Pre-batching processed 1 items
2014-03-04 18:37:53.884 DEBUG PUSH pool-3-thread-7 - /notifications/v1/our device name with application id [com.sybase.sup.components.notification.PushNotificationBuilder]IMO Notification sent successfully.
2014-03-04 18:37:53.884 INFO PUSH pool-3-thread-7 - /notifications/v1/our device name with application id [com.sybase.sup.components.notification.PushListenerServlet]ODP : Notification sent to the device:Notification message sent to messagechannel:
2014-03-04 18:37:53.876 INFO PUSH pool-3-thread-7 - /notifications/v1/our device name with application id [com.sybase.sup.components.notification.PushListenerServlet]------Notification headers are read------------
2014-03-04 18:37:53.875 DEBUG PUSH pool-3-thread-7 - /notifications/v1/our device name with application id [com.sybase.sup.components.notification.PushListenerServlet]Reading settings from appConSettings...
2014-03-04 18:37:53.875 DEBUG PUSH pool-3-thread-7 - /notifications/v1/our device name with application id [com.sybase.sup.components.notification.PushListenerServlet]----------request URL obtained for notification is--------http://mobdev1:8000/notifications/v1/our device name with application id
2014-03-04 18:37:53.875 DEBUG PUSH pool-3-thread-7 - /notifications/v1/our device name with application id [com.sybase.sup.components.notification.PushNotificationBuilder]Notification Mode: Online/Payload Push with Native Notification
2014-03-04 18:37:53.875 INFO PUSH pool-3-thread-7 - /notifications/v1/our device name with application id [com.sybase.sup.components.notification.PushNotificationBuilder]IMO Notification to be processed
2014-03-04 18:37:53.875 DEBUG PUSH pool-3-thread-7 - /notifications/v1/our device name with application id [com.sybase.sup.components.notification.PushNotificationBuilder]Notification Mode2
Thanks in Advance,
Suresh

No sountd notifications on device

Similar Messages

Maybe you are looking for