Log In/Out of hunt group in Jabber

Is it possible to log in/out of hunt group in the Windows Jabber client.
Ideally is would be great to use presence to determine whether a user is available or not

You could use AXL to update the Logged into Hunt Group setting.
You may configure a Webservice to send the requests or even an UCCX script which can be dialed.
The UpdatePhone request provides the hlogStatus function.
https://developer.cisco.com/site/collaboration/management/axl/develop-and-test/documentation/latest-version/axl-soap.gsp

Similar Messages

Prevent 'Logged out of Hunt Group' on 7900 series IP phones

I have a CUCM configuration on 8.2, and have an issue with some 7925 wireless devices that are set up in a "call flow" along side a pair of 7945 devices. If a call comes into either of those devices' extensions, after a set # of seconds of "no answer" "busy" condition, the call is set to move to a Hunt Pilot which then sends a broadcast out to a group of 6 7925 phones so those calls can be answered by staff. However, I ran into a situation yesterday where all but 1 of those devices was powered off, and the 1 powered on was logged out of the Hunt Group. As such, when calls came into either extension, it would ring 2-3 times and then the caller would get a busy tone. After some troubleshooting, we determined that logging that 7925 back into the Hunt Group remedied the problem.
In the interim, I have created a custom SoftKey Template for these devices which removes 'HLog' as an option so they can't inadvertently log out of said Hunt Group, but I have to wonder: are there any conditions under which either the CUCM platform, OR the phone device itself would force a logoff from the Hunt Group WITHOUT user intervention? If so, is there a way to prevent that from occurring?

Hi Josh,
This functionality was only added in CUCM 9.1
Automatically Logout Hunt Member on No Answer
Automatic logout of hunt members was introduced for queuing-enabled hunt pilots in Unified Communications Manager 9.0(1). If an agent does not answer a queuing-enabled hunt pilot call, that agent will be logged off of the hunt group and will not receive additional hunt pilot calls unless he presses the "HLOG" soft key on the phone to log into the hunt pilot. This behavior is not configurable in Unified Communications Manager 9.0(1). In Unified Communications Manager 9.1(1), the administrator can choose whether hunt members remain logged in if the call is not answered.
For more information, refer to "Automatically Logout Hunt Member on No Answer" in the Cisco Unified Communications Manager Administration Guide, and to "Call Queuing" in the Cisco Unified Communications Manager Features and Services Guide.
from;
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/9_1_1/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91_chapter_0100.html#CUCM_RF_CF356549_00
Have you thought about linking back to the first Hunt group if the members of Hunt#2 are unavalable
to give member 1 & 2 a second chance at taking the call? Just a thought
Cheers!
Rob
"A smile relieves a heart that grieves"
- Stones

Ephone logged out of hunt group

In CME I have a hunt group setup so that when someone calls in to the main line it rings ephone 10 if no answer it rings ephone 11. If no one answers these phones it will ring an on a cell-phone that the on call shift has. However, somehow the first phone (ephone 10) got logged out of the hung group and I can not get it to ring anymore. Is there a simple way to log the phone back into the hunt group that I am not seeing? Below is the out put of the show ephone command for that phone. Along with the hunt group configuration.
show ephone 001D.450B.A869
ephone-10 Mac:001D.450B.A869 TCP socket:[5] activeLine:0 REGISTERED in SCCP ver 6 and Server in ver 6
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:7
IP:10.60.8.28 49415 7961 keepalive 13656 max_line 6 DnD HuntGroupLogout
button 1: dn 15 number 206 CH1 IDLE CH2 IDLE huntGroupLogout
button 2: dn 22 number 213 CH1 IDLE CH2 IDLE shared
Username: jharvey Password: 12345
Here is the out put of the show ephone-hunt command
show ephone-hunt
Group 2
type: longest-idle
pilot number: 502, peer-tag 20061
list of numbers:
206, aux-number A502A0100, # peers 1, logout 1, down 1
on-hook time stamp 1389019098, off-hook agents=0
peer-tag dn-tag rna login/logout up/down
[20060 15 0 logout down]
209, aux-number A502A0101, # peers 1, logout 0, down 0
on-hook time stamp 1441176762, off-hook agents=0
peer-tag dn-tag rna login/logout up/down
[20062 18 0 login up ]
only one agent available!
final number: 97433765
preference: 0
preference (sec): 7
timeout: 15, 15
hops: 1
E.164 register: yes
auto logout: no
stat collect: yes

Hi,
I guess you've configured the hunt group to work with overlays on the ephones?
Therefore you should probably have 1 or 2 ephone-dn's with the same number (for each of the hunt group members)?
So ephone 10 should be configured something like this:
ephone 10
mac 001D.450B.A869
1:10(whatever the ephone-dn is) 2o12,13,14 (the hunt list members)
i.e. 1:10 2o12,13,14,15
If any of the overlays or hunt group dn's are missing that might explain why it's not working
Hope this helps...
Please rate useful posts..

Hunt Groups to login

Can you create a hunt group for multiple users to login in CM5.x so as to use it like a helpdesk environment and you can track whether the user has logged in or out of the queue. Any help would be great

Hi Satu,
Just to add a note to the great tips from Pam and James (+5 points each folks :)
Don't feel stupid my friend, there are so many acronyms in this business it will make your head spin :)
ACD = Automatic Call Distribution (calls are distributed between active/logged-in Agents)
This term relates to Call centre applications like UCCX.
As to Hunt Group Login/Logout, sadly this feature is only available CCM 4.2 and CUCM 6.x/7.x with the Login/Logout of Hunt Groups feature (as James nicely noted). This is not available in CCM 4.1.3 or 5.x. Have a look;
Log Out of Hunt Groups
The Log Out of Hunt Groups feature allows phone users to log their phones out from receiving calls that get routed to directory numbers that belong to line groups to which the phone lines are associated. Regardless of the phone status, the phone rings normally for incoming calls that are not calls to the line group(s) that are associated with the phone. The phone provides a visual status of the login state, so the user can determine by looking at the phone whether they are logged in to their line group(s).
The Log Out of Hunt Groups feature also comprises the following components:
The HLog softkey allows a phone user to log a phone out of all line groups to which the phone directory numbers belong. Configure the HLog softkey in the Softkey Layout Configuration window. When the user presses the HLog softkey, the phone screen displays "Logged out of Hunt Group." When the user presses the HLog softkey again to log back in and receive hunt group calls, the "Logged out of Hunt Group" notification on the phone screen clears.
The Hunt Group Logoff Notification service parameter in the Clusterwide Parameters (Device - Phone) section of the Service Parameters Configuration window for the Cisco CallManager service must be configured to enable this feature.
Hunt Group Logoff Notification Service Parameter
The Hunt Group Logoff Notification service parameter in the Clusterwide Parameters (Device - Phone) section of the Service Parameters Configuration window for the Cisco CallManager service provides the option to turn audible ring tones on or off when calls that come in to a line group arrive at the phone and the current status of the phone is logoff. The default value specifies None, which causes the phone not to ring.
The Log Out of Hunt Groups feature, which is device-based, operates differently for non-shared lines and for shared lines.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_2_1/ccmsys/a03rp.html#wp1091630
In the CCM 4.1.x and 5.x trains there is really not an equivilant feature. The best you can do is probably using AC Hunt :(
Hope this helps a little!
Rob

Allowing CFA for a phone in a Hunt Group

I have CCM v5.13. Several users are members of a hunt group, and claim that they used to be able to call forward their phones and not receive any calls from the Hunt Pilot. I've made some changes to the Hunt Pilot, and ever since they say when they call forward their phones, it only works for calls made directly to their DID number , and that calls from the Hunt Pilot still ring on their phones.
I've researched this, and found Bug CSCec54565, which states that Cisco recognizes the issue, but has no plans to fix it. The recommended work around is to call the DID number directly, not through the Hunt Pilot. This doesn't work for my set up because these DID numbers are customer service lines which are published to the public.
I also found, in my research, solution # K00682545, which states that this Hunt Group is Working As Designed, and suggests the same work around, which is calling the DID directly.
My concern is the changes I made in the Hunt Pilot. I'm giving my users the benefit of the doubt when they say they used to be able to call forward all calls, whether they come from the Hunt Pilot or directly. I've set up a test Hunt Pilot, using our phones here in the shop, and I could duplicate their problem.
Can anyone think of a change I could have made in the Hunt Pilot settings that would bring this result, or are these users imaging that they could ever call forward all their incoming calls while belonging to a Hunt Group? Any ideas would be appreciated.

Hi Bethany,
CUCM Hunt Groups/Line Groups have worked this way since at least CCM 4.1(3) :) I never like to doubt users (not a great idea for job preservation) but...I don't see their claim being a valid one.
You have to keep in mind that a call that has routed via the Hunt Pilot will always ignore the CFWD Settings on Hunt Group Member phones. The normal way to control this then is via the Hunt Group Logout of member phones combined with the Hunt Pilot level forward settings.
The following describes how the Call Forward settings on individual Hunt member phones are ignored when presented a call via the Hunt feature. Here is a clip;
Hunting and Call Forwarding
The concept of hunting differs from that of call forwarding. Hunting allows Cisco Unified Communications Manager to extend a call to one or more lists of numbers, where each such list can specify a hunting order that is chosen from a fixed set of algorithms. When a call extends to a hunt party from these lists and the party fails to answer or is busy, hunting resumes with the next hunt party. (The next hunt party varies depending on the current hunt algorithm.) ***Hunting thus ignores the Call Forward No Answer (CFNA), Call Forward Busy (CFB), or Call Forward All (CFA) settings for the attempted party (Line Group member Phones).
From this good doc;
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_0_1/ccmsys/a03rp.html#wp1078922
This is where the Hunt Group Logout comes into play. Sadly I don't think any CUCM 5.x versions support this feature, but the users can look forward to this in your next release (6.X or 7.x)
Log Out of Hunt Groups
The Log Out of Hunt Groups feature allows phone users to log their phones out from receiving calls that get routed to directory numbers that belong to line groups to which the phone lines are associated. Regardless of the phone status, the phone rings normally for incoming calls that are not calls to the line group(s) that are associated with the phone. The phone provides a visual status of the login state, so the user can determine by looking at the phone whether they are logged in to their line group(s).
The Log Out of Hunt Groups feature also comprises the following components:
â¢The HLog softkey allows a phone user to log a phone out of all line groups to which the phone directory numbers belong. Configure the HLog softkey in the Softkey Layout Configuration window. When the user presses the HLog softkey, the phone screen displays "Logged out of Hunt Group." When the user presses the HLog softkey again to log back in and receive hunt group calls, the "Logged out of Hunt Group" notification on the phone screen clears.
â¢The Hunt Group Logoff Notification service parameter in the Clusterwide Parameters (Device - Phone) section of the Service Parameters Configuration window for the Cisco CallManager service must be configured to enable this feature.
The Log Out of Hunt Groups feature, which is device-based, operates differently for non-shared lines and for shared lines.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmsys/a08ipph.html#wp1032225
Hope this helps!
Rob

How to enable HLog for B-ACD Hunt Group

We are using B-ACD for imcoming calls, the hunt group for BACD has 5 members. I want people to be able to login/logoff from this hunt group.
I have this working with the DND button, but then the phone doesn't ring when the extension is dailed directly. So it seems the alternative is using another feature/button called "Hlog".
I've added the HLog softkey but nothing happens when its pressed. I can't seem to find instructions on what else might need to be done to enable HLog.
Here is a bit of the related config info
ephone-template 16
softkeys idle Redial HLog Cfwdall Pickup Dnd Mobility
softkeys seized Cfwdall Endcall Redial Pickup Gpickup Callback
softkeys connected Trnsfer Endcall LiveRcd Hold Mobility
ephone-dn 15 dual-line
number 206
no-reg primary
label 206
description Kathy
name Kathy
call-forward busy 299
call-forward noan 299
timeout 10
ephone 6
device-security-mode none
video
mac-address 0021.1BFC.BF2B
ephone-template 16
max-calls-per-button 2
username "kathy"
password 1112
type 524G
button 1:15
ephone-hunt 50 sequential
pilot A888
list 204, 205, 201, 206
timeout 8, 8, 8, 8
no-reg pilot
statistics collect
auto logout 3
description *** CCA BACD ***
display-logout All agents logged out

We still don't have Logging in and out of the BACD Hunt group working.
The #350 and *350 don't seem to work. On the phone when I dial them it connects for a second then disconnects, no feedback if it worked. But when I try calling our business number the phone still gets rung in the hunt group sequence. So the phone isn't getting logged out.
On some of the phones I can see the "HLog" button but when pressed it says "that key is not active here".

CCM 4.2 and Hunt Group pickup

Hello,
do someone know if the hunt group pickup feature is now enabled on the CCM 4.2?
Thanks in advance
Daniele

No. Call pickup is still not possible for hunted calls on 4.2. However, there is a new feature that may ease the pain of this. The "hlog" softkey offers the ability for afk users to "log out" of a hunt group while they are away. That way the call does not hunt to them in the first place. You can review this feature and other interesting things in the release notes: http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/prod_release_note09186a00805f1470.html

Hunt Group Fallback

We are running CUCM v9 and are trying to set up the following configuration:
A heldesk hunt group which every phone in the company can log in and out of as they need
When a call comes into the helpdesk hunt group and is not answered for 20 seconds the call gets diverted to ALL phones in the company as a fallback from helpdeskThis call to ALL other phones cannot be a shared DN
Any ideas on how I can implement this? I've been racking my brain for hours. I first though of two separate hunt groups but realised that you can't log in and out of individual hunt groups, its either all or nothing. Then I was thinking group pickup??
Thanks

Create hunt pilot, point to new hunt group, in the hunt group point to 2 new line groups, where line group one points to all phones in longest idle or top down fashion, and the second is defined as broadcast.
On the hunt pilot setup call forwarding to the desired destination and setup the hunt timer as desired.
Chris

Hunt Group Issue - DN being skipped over

Hello,
I am trying to set up a Hunt Group which hunts, top down, to four different extensions (A,B,C,D).
This is working as expected apart from one particular extenstion...C. When start or middle of the Line Group this extension gets skipped over completely even though the user is logged into their phone and direct calls to that extension get through fine. When C gets put to the end of the Hunt Group the call gets terminated rather than the extension ringing with a "Line Busy" message.
I have checked the Directory Number and Extension Mobility Profile settings of extension C against those that do work (A,B,D) and I believe everything is set the same...I can see no obvious reasons why C will not ring. I have also checked with the user that no DND/call forwards are set up. I have also created an entirely new Directory Number and associated it with user C's EM-Profile...the same thing happens.
Am I potentially missing something here? For the life of me cannot see why this is happening.
Thanks,
-David

David,
Two things come to mind..
1. Does the user have HLOG softkey? If so perhaps the user has accidentally logged out of the hunt group
2. Have you tried logout/login back to EM?
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"

Hunt group type Set up with outside ext numbers ie Cell phones

Using CUCM 9.1
Is there a quick and easy way to create a hunt group type set up using outside (cell phone numbers)?
The scenario will be one (person who will be ON Call) using an internal DID that is forwarded to to a cell phone of the oncall person that particular week. If no answer it would forward to the next line group of 4 members and also try their cell phones. After this it would simply repeat the entire process. So far it looks like a solution may be possible with single line reach perhaps?
Any insight would be grealy appreciated.
Dave

Hello,
I set up something like this on CUCM 8.0 a couple of years ago.
I used the Mobile Connect feature as you suggest and it worked ok after some playing about with the timers.
The main problem was that there was no way for the remote users to log out of the hunt group. They could disable Mobile Connect using the IVR but the calls would still ring on their deskphones - if you log out of the phones (i.e. Extension Mobility) before leaving the office this problem should not occur.
The other issue was how long calls took to connect especially if a couple of people in the group did not answer. We actually recorded a message asking callers to be patient that was played when the call was first received (we were using UCCX to do the IVR and call transfer).
Hope this is of use.

CUCM 8.6 - Call Forward All Doesn't Work With DN In Hunt Group

Hello,
I'm trying to make a hunt group that's sole purpose is to dial out to our Help Desk member's cell phone (on-call after hours). The idea is that we want the hunt group to broadcast the call to the on-call engineers. Whoever picks up first takes the call.
At least that's the idea now. They may want to change that to - ring primary on-call cell phone, if no answer ring secondary on-call engineer.
The target cell phones will change every week and I wanted to give the supervisor a means of changing the numbers through the ccmuser page.
I created two DNs and placed them in a hunt group, each with call forward all to a cell phone number.
It seems that the hunt group ignores the call forward all setting and that is by design (https://supportforums.cisco.com/document/9126/cisco-callmanager-call-forward-all-cfa-does-not-work-if-line-hunt-group).
Does anyone else have any suggestions on how to accomplish this?

That's correct, what you're seeing is WAD, this topic has been discussed plenty of times before, the only option you have is SNR

CVP 7.0(2) SIP RNA Timer with CUCM Hunt Group

I have a very simple ICM 7.5(9) script which simply assigns a call type then forwards to a label on CUCM 7.1(5), which is a hunt pilot containing a hunt list with 2 line groups...a circular LG with 10 members (RNA reversion timeout of 20 sec), followed by a broadcast LG with different 10 members. There is no CFNA/CFB forwarding set up on the hunt pilot.
In CVP, the SIP RNA timer is set on for this DN at 120 seconds, and I can see that get set in CVP logs (IP addresses and dialed numbers modified to protect customer data):
41762417: 10.100.1.41: Dec 03 2012 20:23:28.977 -0500: %CVP_7_0_SIP-7-CALL: {Thrd=Pool:SIP[7059609]} Matched 666333315555551111 to proxy.customer.uc
41762418: 10.100.1.41: Dec 03 2012 20:23:28.977 -0500: %CVP_7_0_SIP-7-CALL: {Thrd=Pool:SIP[7059609]} Using Local Static Route for sip:[email protected]
41762419: 10.100.1.41: Dec 03 2012 20:23:28.977 -0500: %CVP_7_0_SIP-7-CALL: {Thrd=Pool:SIP[7059609]} Matched 666333315555551111 to TimeoutMatcher: patterns like 66633331> will use RONA of 120
41762420: 10.100.1.41: Dec 03 2012 20:23:28.977 -0500: %CVP_7_0_SIP-7-CALL: {Thrd=Pool:SIP[7059609]} CALLGUID = 0B19E39A3CE811E28B7DA21700DE4950 LEGID = 0B19E39A3CE811E28B7DA21700DE4950-135458420897716680 - [OUTBOUND]: INVITE TO <sip:[email protected];transport=udp> FROM "--CVP" <sip:[email protected]:5060> EXPIRES[120] 100REL[Unsupported]
The hunt group then begins hunting, and can be answered normally. However, a CANCEL is sent at 60 seconds, and I am not sure why:
From the gateway:
2106715: Dec 3 20:24:29.095: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
CANCEL sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.100.1.5:5060;branch=z9hG4bK2C171513C0
From: "--CVP" <sip:[email protected]>;tag=20687DD0-DAF
To: <sip:[email protected]>
Date: Tue, 04 Dec 2012 01:23:29 GMT
Call-ID:
[email protected]
CSeq: 101 CANCEL
Max-Forwards: 70
Timestamp: 1354584269
Reason: Q.850;cause=19
Content-Length: 0
From CUCM SDI traces:
12/03/2012 20:24:29.169 CCM|//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 10.100.3.30 on port 43568 index 566129 with 389 bytes:
CANCEL sip:[email protected]:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 10.100.3.30:5060;branch=z9hG4bK51cac6f4-76fb29a5-78d5dd99-9a021233-1
Call-ID: [email protected]
From: "--CVP" <sip:[email protected]:5060>;tag=ds229f1b0f
To: <sip:[email protected];transport=udp>
CSeq: 1 CANCEL
Content-Length: 0
I am trying to determine which timer is limiting the hunt to 60 seconds.
Can anyone suggest where I might begin looking?
Thanks so much!!!

I've run into a similar problem recently with a CVP 8.5(1) SIP deployment and have found in the CVP documentation that the RNA Timeout is a range configurable between 5 and 60 seconds.
You can enter a larger value through OAMP on the Call Server-->SIP-->Advanced Configuration tab but when you Save and Deploy, it reverts back to the max of 60 seconds. The CVP help file indicates the 5-60 second range.
Regards,
Matt

Setting up Hunt Group using an extension number instead of a pilot number

Hi Guys,
I would like to set up a hunt group. My question is can I use a real extension number assigned to a phone to be a pilot number instead of creating a new pilot number.
The requirements are if no one is answering a call to an extension 1000 (extension 1000 is assigned to a user) it should be forwarded to 1001, 1002, 1003 and back to 1000. I was thinking of using 1000 as pilot number. Is that possible ?
Thanks Guys

Hi Guys,
Thank you very much for your suggestions. Here is what I have done:
With Manish's solution the call forwarding works upto the third phone then it got disengaged. Looks like there is a timer I need to increase so that the call will not time out. Could you please let me know which timer I have to adjust. I have checked the max forwards hops and they are set to 15-20 so don't think this is an issue.
With regard to Jamie's solution, I have created a separate partition and assigned same DN 1000 to it. It works great when I call from inside. However when I call it from outside using the full E164 number the call goes to 1000 then it just go to the voicemail of 1000 if not answered. I have removed the settings under DN page so that it will not go to voicemail. After doing this the phone with extension 1000 keeps ringing until it times out. Not sure where the issue is here.
I have given a suggestion to my customer to use a new pilot number with hunt groups. I have tested this as well. When I call it from outside the call goes to all the five phones and it just keep going into circle until someone answered and that's what I want. But when I call DN 1000 from inside it goes to all the five phones and when I reaches to the last phone configured under the line group member the call then just dropped out. Is there a way to fix this so that when someone just dial the extension number from inside all the phones keep ringing in circle manner and did not drop until someone has answered it.
Thanks a lot guys.
Regards

Standby problem - log numbers out of sequence

Hi everyone! I am on 10.2.0.3.
My physical standby stopped applying logs because all of a sudden the logs went out of sequence. See errors below - after seq 7975 & 7976 seq# 7974 showed up again:
Recovery of Online Redo Log: Thread 1 Group 200 Seq 7974 Reading mem 0
Mem# 0: /db/data3/FSPRD/stby_redo02.log
Mem# 1: /db/data4/FSPRD/stby_redo02_02.log
Thu Dec 18 16:14:58 2008
RFS[23]: Successfully opened standby log 100: '/db/data1/FSPRD/stby_redo01.log'
Thu Dec 18 16:15:01 2008
RFS[25]: Successfully opened standby log 300: '/db/data5/FSPRD/stby_redo03.log'
Thu Dec 18 16:15:01 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[37]: Successfully opened standby log 400: '/db/data7/FSPRD/stby_redo04.log'
Thu Dec 18 16:15:02 2008
RFS[24]: Successfully opened standby log 200: '/db/data3/FSPRD/stby_redo02.log'
Thu Dec 18 16:15:03 2008
Media Recovery Waiting for thread 1 sequence 7975 (in transit)
Thu Dec 18 16:15:03 2008
Recovery of Online Redo Log: Thread 1 Group 100 Seq 7975 Reading mem 0
Mem# 0: /db/data1/FSPRD/stby_redo01.log
Mem# 1: /db/data2/FSPRD/stby_redo01_02.log
Media Recovery Waiting for thread 1 sequence 7976 (in transit)
Thu Dec 18 16:15:07 2008
Recovery of Online Redo Log: Thread 1 Group 200 Seq 7974 Reading mem 0
Mem# 0: /db/data3/FSPRD/stby_redo02.log
Mem# 1: /db/data4/FSPRD/stby_redo02_02.log
MRP0: Background Media Recovery terminated with error 355
Thu Dec 18 16:15:12 2008
Errors in file /db/dbdump/FSPRD/bdump/fsprd_mrp0_11351.trc:
ORA-00355: change numbers out of order
ORA-00353: log corruption near block 2 change 4994299896 time 12/18/2008 16:14:57
ORA-00312: online log 200 thread 1: '/db/data4/FSPRD/stby_redo02_02.log'
ORA-00312: online log 200 thread 1: '/db/data3/FSPRD/stby_redo02.log'
Managed Standby Recovery not using Real Time Apply
Thu Dec 18 16:15:12 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[37]: Successfully opened standby log 100: '/db/data1/FSPRD/stby_redo01.log'
Thu Dec 18 16:15:13 2008
Recovery interrupted!
Thu Dec 18 16:15:13 2008
Errors in file /db/dbdump/FSPRD/bdump/fsprd_mrp0_11351.trc:
ORA-00355: change numbers out of order
ORA-00353: log corruption near block 2 change 4994299896 time 12/18/2008 16:14:57
ORA-00312: online log 200 thread 1: '/db/data4/FSPRD/stby_redo02_02.log'
ORA-00312: online log 200 thread 1: '/db/data3/FSPRD/stby_redo02.log'
Thu Dec 18 16:15:13 2008
MRP0: Background Media Recovery process shutdown (FSPRD)
Thu Dec 18 16:15:19 2008
I of course restarted the managed recovery and everything went fine from this point on - but I could not find the root cause of this problem.
Anybody has any ideas - or experienced this before?
TIA.

I'm afraid you're hitting bug 6039415 ORA-355 can occur during real time apply, the good news: there's a patch available.
HTH
Enrique

Lync RSG Hunt Group not working as expected, not getting calls on lync clients

I have created an Hunt Group in Lync. When i dial the number i do get the welcome message but after that it does not get forwarded to the test user which is configured in the Group. (Created a Queue and selected the group here and assigned this to the workflow)
Error on Lync report:
Request: BYE Response: 200
Diagnostic ID: 26029 Category: Unexpected
Component: Response Group application
Reason:
Call is disconnected because of invalid configuration.
Description:
Call is disconnected because of invalid configuration.
Error in Event Viewer:
The workflow runtime encountered a critical error.
Failure occurrences: 8, since 4/17/2012 7:47:14 AM.
The last encountered error was from a workflow with the display name: TestRG, the URI: sip:[email protected], and the GUID: 810c628c-d0c5-4b31-b8d5-f61595def5b0
Suhas

HI,
Do you deploy standard lync server or enterprise lync server?
If enterprise lync server, please log in SQL server and search the rgsdyn--dbo.ActiveFEInstance. Please check you can find the FE server FQDN and the port 8404 in this table.
Please running the Lync server logging tool on the FE server to find why the Response Group can not transfer the calls to the agent.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Log In/Out of hunt group in Jabber

Similar Messages

Maybe you are looking for