Problems with the Supervisor Monitoring configuration

Hello everyone,

Please help me with and error that I have with a supervisor monitoring procedure.

I configured and agent with a leader privilegies, and a mcu DN (contact - 192.168.170.6:5160; prefix - conf=; service-type - mcu), and the options tab in the Sip Server (scope, mode, intrusion,etc.).

I logged in with the supervisor user, so i can see all the agents that i put in the agent group, i push the button monitor, and a system message appears with “monitoring of agent xxxxxx is started”.

But when the monitored agent make or receive a call, the Voice Interaction Monitoring windows never appears.

So I watch the Sip Server log, and in the monitoring event i can see:

16:10:01.881 — CIFace::Event —
16:10:01.881:(1) SIPTR(177): complete
16:10:01.881:(1) SIPTR(176): Step 0 - SipTransactionConnectCompleteAnswer(177) complete
16:10:01.881:(1) SIPTR(176): complete
16:10:01.881:(1) SIPCM: transaction SipScenario(176) complete
16:10:01.881:(1) Selected for Dn (geo-loc:partitionId:cpdCapability): Service MSSIP (geo-loc, priority[0], capacity 0 (0% of -2))
16:10:01.881 SIPCONN(4001): set monitor 048f0748, 0486ba1c
16:10:01.881:(1) SIPCALL(9): add party ‘4001’
16:10:01.881 – created party_info_tspp 48c5a78
16:10:01.881 – created aTmParty 48b9310
16:10:01.881 SetRole: Observer for 4001.48b9310-418c260:1
16:10:01.881 – AddParty to 418c260: 4001.48b9310-418c260:1
16:10:01.881 – new TSCP call leg 3
16:10:01.881 – call leg created leg_id=3
16:10:01.881 CreateParty new internal: 4001.48b9310-418c260:1
16:10:01.881:(1) Call 9 dn 4001 SetPartyId 27
16:10:01.881:(1) SIPTR(176): Begin step 0 - SipTransactionConferenceParty(178)
16:10:01.881 SIPPARTY(4003): +mcu
16:10:01.881 SIPCONN(MSSIP): set monitor 048f1278, 04613048
16:10:01.881 SIPCONN(4003): re-invite-connected
16:10:01.881 SIPCONN(MSSIP): re-invite-null
16:10:01.881 SIPCONN(MSSIP): GetOffer
16:10:01.881 SIPCONN(MSSIP): GetOffer::SendInvite
16:10:01.881:(1) SipDialog: set monitor 048f12ec
16:10:01.881 SIPCONN(MSSIP): main dialog 0 created
16:10:01.881 SIPCONN(MSSIP): AddInviteExtraHeaders: originator empty, X-Genesys-Orig not added.
16:10:01.881 SIPCONN(MSSIP): Local contact: ‘sip:4003@192.168.170.6:5060’
16:10:01.881 SIPCONN(MSSIP): InitiateDialog: preparing a 3pcc request
16:10:01.881:(1) SIPDLG[32]: register TRN[110]
16:10:01.881:(1) SIPDLG[32]: TRN[110] flags set to 0x6
16:10:04.132:(1) ERROR: ffffffff, InitiateDialog(requestUri,*device, from, to, content, extraHeaders, false), SipConnection.cpp,3023
16:10:04.132:(1) ERROR: ffffffff, SendInvite(body,0), SipConnectionConnect.cpp,518
16:10:04.132:(1) ConnectAbort
16:10:04.132 SIPCONN(4003): ClrMediaPeer
16:10:04.132 SIPCONN(MSSIP): ClrMediaPeer
16:10:04.132:(1) SIPTR(178): failed
16:10:04.132:(1) SIPTR(176): Step 0 - SipTransactionConferenceParty(178) failed
16:10:04.132:(1) SIPTR(176): failed
16:10:04.132:(1) SIPCM: transaction SipScenario failed
16:10:04.133 SIPCONN(MSSIP): CONNCHECK: dialog=0
16:10:04.133 SIPCONN(MSSIP): CONNCHECK: dialog=0
16:10:04.133:(1) invalid mcu channel detached from party ‘4003’
16:10:04.133 SIPCONN(MSSIP): ClrMediaPeer
16:10:04.133 SIPPARTY(4003): -mcu
16:10:04.133 SIPCONN(MSSIP): set monitor 048f1278, 00000000
16:10:04.133 SIPCONN(MSSIP): Active transaction(110) discarded
16:10:04.133:(1) SipDialog: ClearCall(phone=0,state=0)
16:10:04.133:(1) SipDialog::Terminate(state=0,reason=0)
16:10:04.133:(1) SipDialog: set monitor 00000000
16:10:04.133 SIPCONN(MSSIP): DetachMediaPeer
16:10:04.133:(1) PI: 00 S[CI]D[4003]C[*D[4003]]MC[!C[!D[MSSIP]]]P[90995157940]
16:10:04.133:(1) PI: 00 S[CA]D[90995157940]C[*D[90995157940]]P[4003]
16:10:04.133:(1) PI: 01 S[NN]D[4001]C[*D[4001]]P[-] - should be deleted
16:10:04.133:(1) check linked party
16:10:04.133:(1) SIPCM: delete party 4001:27
16:10:04.133 SIPCONN(4001): set monitor 048f0748, 00000000
16:10:04.133 SIPCONN(4001): DetachMediaPeer
16:10:04.133:(1) SIPCALL(9): delete party ‘4001’
16:10:04.133:(1) CALLSTATE(a:2,d:0,i:0,e:1,r:0,o:0)
16:10:04.133:(1) party ‘4003’ is not connected to the mcu
16:10:04.133:(1) party ‘90995157940’ is not connected to the mcu
16:10:04.133:(1) conference is detached from the call
16:10:04.133:(1) call1 9 idle
16:10:04.133:(1) SIPS:LOGBLOCK:END:SIPDATA:]
16:10:12.026:(1) SIPS:LOGBLOCK:BEGIN:SIPDATA:[
16:10:12.026:(1) Received [476,UDP] 4 bytes from 192.168.170.6:38936 <<<<<

As you can see, there is a problem in the InitiateDialog command or something else i not configure, mcu connections issues and channels.

Please help me with this, thanks.

When you login as supervisor you also have a SIP Endpoint, correct?
Which one are you using?
Can you post a full snippet?

Hi,

Thanks for your help,

Yes, I have the Interaction_Workspace_SIP_Endpoint_G273_8020202_ENU in the supervisor IWS and in the agents desktops.

Which snippet do you want?? Sip server, SIP endpoint?? , IWS??

Thanks

SIP Server and SIP Client

Hi,

I tried to upload the logs, but an error occurs, a message is displayed “Folde for upload is full, try with a smaller file or contact the administrator”, my rar or zip file is 90 Kb, how can i upload the files?

Thanks for your help.

Oh you can’t here it is disabled, but upload somewhere else and post the link

HI,

I send you the link:

http://filestoragepro.net/?d=510A94D91

Thanks.

Can’t download…asks for a suscription fee…???

HI,

Sorry, try with this, it works fine, i tested it. :-\

http://www.mediafire.com/?nan85aj4l04dh27

What are you using as conference server? StreamManager or MediaServer??

Hi,

I am using Media Server like a conference server.

I was reviewing the Sip log, and in fact when the Sip tries to init a 3pcc conference (i think monitoring uses the same process for conferences) an error appears.

Can you post RM logs too?
Are you able to do a simple conference?

Show the DN config.

Hi guys,

I was on a project, and i can’t follow this post :'(. I back with this issue.

Hi Timur,

What Dn’s config do you request? extension? trunk?

Thanks for your he

Hi cavagnaro,

What is RM?

And it’s correct, i can’t do a simple conference call, so i was thinking that monitoring uses the same procedure, so if conference desn’t work either monitoring.

Thanks for your help.

RM is ResourceManager,part of GVP deployment. RM is component which provide proxy,monitoring,etc SIP services. Physical conference is thing of MCP or StreamManager,it depend on your env - which component are you using? Did you check all required deployment steps?