" /> TMonitor and SIP - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: TMonitor and SIP  (Read 4564 times)

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
TMonitor and SIP
« on: March 01, 2007, 08:11:29 AM »
Advertisement
Hi, all,

I am having a problem with getting TMonitor to work with SIP TServer.
The problem in a nutshell is that instead of monitoring, I am getting a three-party talk.

Here is a log -- any ideas?

I was hoping that MCU would be able to do this for me without me specifying a=recvonly in SDP.

[size=8pt]
[font=Verdana][color=green]
10:46:50.762 Trc 04541 RequestMonitorNextCall received from 484 (0066 CTISIP_Client)
message RequestMonitorNextCall
AttributeThisDN '6501'
AttributeOtherDN '6003'
AttributeMonitorNextCallType 1 (MonitorAllCalls)
AttributeReferenceID 6
10:46:50.762 -- created: CRequest@01C0F140 RequestMonitorNextCall-CTISIP_Client[484]/6
10:46:50.762 +++ CIFace::Request +++
  -- new invoke
  Parsed: RequestMonitorNextCall
  From: CTISIP_Client[484]/6
  Numbers: +<6501> +<6003>
  Status: parsed:1 queued:0 sent:0 acked:0 preevent:0 event:0 context:0 transferred:0
  -----
  -- validate
  -- state check: ok
  SIPTS_IFace::QServe()01C0F140
  CIFace: Sent CRequest@01C0F140 RequestMonitorNextCall-CTISIP_Client[484]/6
@10:46:50.7620 [BSYNC] Trace: Send to backup (TServer_SIPPremise_Backup) [404]: message EventSwitchInfo
attr_#1005 0
attr_#1004 762
attr_#1003 1172713610
attr_#1002 1447
attr_#1001 2
attr_#1000 131072
AttributeTransferredNetworkCallID 9437282
AttributeCallID 75
AttributeNetworkNodeID 0
AttributeNodeID [54] 05 00 00 00..
AttributeProtocolVersion 1
@10:46:50.7620 [BSYNC] Trace: Sent
sipcs: 10:46:50.762 Monitor mode: assume 'normal'
sipcs: 10:46:50.762 Monitor scope being set to default-monitor-scope
@10:46:50.7620 [0] 7.2.100.42 send_to_client: message EventMonitoringNextCall
AttributeEventSequenceNumber 0000000000000606
AttributeTimeinuSecs 762000
AttributeTimeinSecs 1172713610 (10:46:50)
AttributeReferenceID 6
AttributeThisDN '6501'
AttributeOtherDN '6003'
AttributeThisDNRole 10
AttributeOtherDNRole 2
AttributeMonitorNextCallType 1 (MonitorAllCalls)
10:46:50.762 Trc 04542 EventMonitoringNextCall sent to 484 (0066 CTISIP_Client)
@10:46:50.7620 [0] 7.2.100.42 distribute_event: message EventMonitoringNextCall
AttributeEventSequenceNumber 0000000000000607
AttributeTimeinuSecs 762000
AttributeTimeinSecs 1172713610 (10:46:50)
AttributeThisDN '6003'
AttributeOtherDN '6501'
AttributeThisDNRole 2
AttributeOtherDNRole 10
AttributeMonitorNextCallType 1 (MonitorAllCalls)
@10:46:50.7620 [ISCC] Debug: Translate: '' -> ''; result 1 ()
10:46:50.762 Trc 04542 EventMonitoringNextCall sent to 496 (0065 CTISIP_Client)
10:46:50.762 Trc 04542 EventMonitoringNextCall sent to 452 (0006 StatServer)
10:46:50.762 Trc 04542 EventMonitoringNextCall sent to 440 (0005 Rpt_StatServer)
10:46:50.778 Trc 04542 EventMonitoringNextCall sent to 428 (0004 StatServer)
10:46:50.778 Trc 04542 EventMonitoringNextCall sent to 416 (0003 Rpt_StatServer)
sipcs: 10:46:50.778 dn[6003] is not on the call. Will postpone monitoring
  Response (0): for CRequest@01C0F140 RequestMonitorNextCall-CTISIP_Client[484]/6
  FinishRequest CRequest@01C0F140 RequestMonitorNextCall-CTISIP_Client[484]/6
  IFace stats: q=280 s=4294967016
  -- complete
10:46:50.778 --- CIFace::Request ---
10:46:50.778 -- deleted: CRequest@01C0F140 RequestMonitorNextCall-CTISIP_Client[484]/6
-AP[6945]->-416 @10:46:51.8400
-Ap[6945]-<-416 @10:46:51.8400
-AP[7396]->-440 @10:46:56.0280
-Ap[7396]-<-440 @10:46:56.0280
-AP[4]->-496 @10:46:58.1060
-Ap[4]-<-496 @10:46:58.1060

sipcs: 10:47:01.122 Sending  [376,UDP] 462 bytes to 172.30.0.222:5065 >>>>>
INVITE sip:victor@172.30.0.222:5065 SIP/2.0
From: <sip:gsipsync>;tag=E06FE6D1-2F67-4DF2-8DDB-18030FC07D7A-1
To: <sip:gsipsync>;tag=3B47ED79-9ABE-4D09-9908-39FF324C0438-1
Call-ID: 289A0BB2DF73437fA79AD5FB5133C52C@gsipsync
CSeq: 10181 INVITE
Content-Length: 0
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10698
Contact: sip:panda@172.30.0.222:5060
Session-Expires: 20;refresher=uac
Min-SE: 10
Supported: timer



sipcs: 10:47:01.122 Received [376,UDP] 472 bytes from 172.30.0.222:5065 <<<<<
SIP/2.0 200 OK
From: <sip:gsipsync>;tag=E06FE6D1-2F67-4DF2-8DDB-18030FC07D7A-1
To: <sip:gsipsync>;tag=3B47ED79-9ABE-4D09-9908-39FF324C0438-1
Call-ID: 289A0BB2DF73437fA79AD5FB5133C52C@gsipsync
CSeq: 10181 INVITE
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10698;received=172.30.0.222
Contact: sip:victor@172.30.0.222:5065
Session-Expires: 20;refresher=uac
Min-SE: 10
Require: timer
Supported: timer
Content-Length: 0



sipcs: 10:47:01.122 Sending  [376,UDP] 353 bytes to 172.30.0.222:5065 >>>>>
ACK sip:victor@172.30.0.222:5065 SIP/2.0
From: <sip:gsipsync>;tag=E06FE6D1-2F67-4DF2-8DDB-18030FC07D7A-1
To: <sip:gsipsync>;tag=3B47ED79-9ABE-4D09-9908-39FF324C0438-1
Call-ID: 289A0BB2DF73437fA79AD5FB5133C52C@gsipsync
CSeq: 10181 ACK
Content-Length: 0
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10698


-AP[8341]-<-416 @10:47:01.8400
-Ap[8341]->-416

sipcs: 10:47:03.403 Received [376,UDP] 828 bytes from 172.30.0.200:5060 <<<<<
INVITE sip:6003@172.30.0.222 SIP/2.0
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REFER, NOTIFY, REGISTER
Via: SIP/2.0/UDP 172.30.0.200:5060;branch=z9hG4bK45e6ab1b11c38515eb8
Max-Forwards: 69
To: <sip:6003@172.30.0.222>
From: "7000" <sip:7000@192.168.100.251>;tag=32fe006c
Call-ID: 108-1985@172.30.0.200
CSeq: 1000311362 INVITE
Contact: sip:7000@172.30.0.200;transport=UDP
P-Asserted-Identity: "7000" <sip:7000@192.168.100.251>
Remote-Party-ID: "7000" <sip:7000@192.168.100.251>;party=calling;privacy=off
Cisco-Guid: 3863002062-3705425820-2839067314-2977428030
User-Agent: SHOUT 4.0.2v15
Content-Type: application/sdp
Content-Length: 176

v=0
o=SHOUT 0 0 IN IP4 172.30.0.200
s=SIP call via SHOUT
c=IN IP4 172.30.0.200
t=0 0
m=audio 16760 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000

sipcs: +dialog [0:00@01821958]
sipcs: +dialog [0:00@01822b60]
sipcs: CInf[0x0181ba50]
sipcs: dbg=>ProcessNewLinkedDialogs::1

sipcs: 10:47:03.403 Sending  [376,UDP] 474 bytes to 172.30.0.222:5065 >>>>>
INFO sip:victor@172.30.0.222:5065 SIP/2.0
From: <sip:gsipsync>;tag=E06FE6D1-2F67-4DF2-8DDB-18030FC07D7A-1
To: <sip:gsipsync>;tag=3B47ED79-9ABE-4D09-9908-39FF324C0438-1
Call-ID: 289A0BB2DF73437fA79AD5FB5133C52C@gsipsync
CSeq: 10182 INFO
Content-Length: 44
Content-Type: application/gsipsync
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10699
Contact: sip:panda@172.30.0.222:5060

1=1
2=357
3=108-1985@172.30.0.200
4=267

sipcs: 10:47:03.403 trunk ip addr 172.30.0.200
sipcs: Reg. Info: dn[7000]<=cme[Trunk] Incoming Invite
sipcs: 10:47:03.403 dispatchDE: dlg[357]
sipcs: UK-PEM:HANDLE(NON-CONNECTED):<<EVENT(12)<<DLG[357]
sipcs:  dialog [357:01@01821958]: << Event 12 << TRN[11262]
sipcs: 10:47:03.403 Stored This SDP [357]

sipcs: 10:47:03.403 Sending  [376,UDP] 506 bytes to 172.30.0.222:5065 >>>>>
INFO sip:victor@172.30.0.222:5065 SIP/2.0
From: <sip:gsipsync>;tag=E06FE6D1-2F67-4DF2-8DDB-18030FC07D7A-1
To: <sip:gsipsync>;tag=3B47ED79-9ABE-4D09-9908-39FF324C0438-1
Call-ID: 289A0BB2DF73437fA79AD5FB5133C52C@gsipsync
CSeq: 10183 INFO
Content-Length: 76
Content-Type: application/gsipsync
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10700
Contact: sip:panda@172.30.0.222:5060

1=1
2=358
3=630AEC66-6008-4D70-8D4D-6B60119331CD-179@172.30.0.222
4=267


sipcs: 10:47:03.403 Sending  [376,UDP] 1059 bytes to 172.30.0.238:8093 >>>>>
INVITE sip:6003@172.30.0.238:8093 SIP/2.0
From: "7000" <sip:7000@192.168.100.251>;tag=32fe006c
To: <sip:6003@172.30.0.222>
Call-ID: 630AEC66-6008-4D70-8D4D-6B60119331CD-179@172.30.0.222
CSeq: 1 INVITE
Content-Length: 176
Content-Type: application/sdp
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10701
Contact: <sip:172.30.0.222:5060>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, REFER, NOTIFY, REGISTER
Max-Forwards: 68
P-Asserted-Identity: "7000" <sip:7000@192.168.100.251>
Remote-Party-ID: "7000" <sip:7000@192.168.100.251>;party=calling;privacy=off
Cisco-Guid: 3863002062-3705425820-2839067314-2977428030
User-Agent: SHOUT 4.0.2v15
Call-Info: <http://genesyslab.com>; 108-1985%40172.30.0.200;gen-rt=32fe006c;gen-lt=E06FE6D1-2F67-4DF2-8DDB-18030FC07D7A-221
Session-Expires: 1800;refresher=uac
Min-SE: 90
Supported: timer

v=0
o=SHOUT 0 0 IN IP4 172.30.0.200
s=SIP call via SHOUT
c=IN IP4 172.30.0.200
t=0 0
m=audio 16760 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000

sipcs: 10:47:03.403 dispatchDE: dlg[358]
sipcs: UK-PEM:HANDLE(NON-CONNECTED):<<EVENT(0)<<DLG[358]
sipcs:  dialog [358:02@01822b60]: << Event 00 << TRN[11265]
sipcs: 10:47:03.403 Stored Other SDP [358]

sipcs: 10:47:03.403 Received [376,UDP] 389 bytes from 172.30.0.222:5065 <<<<<
SIP/2.0 200 OK
From: <sip:gsipsync>;tag=E06FE6D1-2F67-4DF2-8DDB-18030FC07D7A-1
To: <sip:gsipsync>;tag=3B47ED79-9ABE-4D09-9908-39FF324C0438-1
Call-ID: 289A0BB2DF73437fA79AD5FB5133C52C@gsipsync
CSeq: 10182 INFO
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10699;received=172.30.0.222
Contact: sip:victor@172.30.0.222:5065
Content-Length: 0



sipcs: 10:47:03.403 Received [376,UDP] 389 bytes from 172.30.0.222:5065 <<<<<
SIP/2.0 200 OK
From: <sip:gsipsync>;tag=E06FE6D1-2F67-4DF2-8DDB-18030FC07D7A-1
To: <sip:gsipsync>;tag=3B47ED79-9ABE-4D09-9908-39FF324C0438-1
Call-ID: 289A0BB2DF73437fA79AD5FB5133C52C@gsipsync
CSeq: 10183 INFO
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10700;received=172.30.0.222
Contact: sip:victor@172.30.0.222:5065
Content-Length: 0



sipcs: 10:47:03.403 Received [376,UDP] 355 bytes from 172.30.0.238:1111 <<<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10701
From: "7000" <sip:7000@192.168.100.251>;tag=32fe006c
To: <sip:6003@172.30.0.222>;tag=ac5084d5011c4b20aea9f6326ca31285
Call-ID: 630AEC66-6008-4D70-8D4D-6B60119331CD-179@172.30.0.222
CSeq: 1 INVITE
User-Agent: RTC/1.2
Content-Length: 0


sipcs: 10:47:03.403 dispatchDE: dlg[358]
sipcs: UK-PEM:HANDLE(NON-CONNECTED):<<EVENT(1)<<DLG[358]
sipcs:  dialog [358:02@01822b60]: << Event 01 << TRN[11265]

sipcs: 10:47:03.403 Received [376,UDP] 356 bytes from 172.30.0.238:1111 <<<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.30.0.222:5060;branch=z9hG4bK7E8C56E5-A57F-4D13-96E3-AA158F1ECC6C-10701
From: "7000" <sip:7000@192.168.100.251>;tag=32fe006c
To: <sip:6003@172.30.0.222>;tag=ac5084d5011c4b20aea9f6326ca31285
Call-ID: 630AEC66-6008-4D70-8D4D-6B60119331CD-179@172.30.0.222
CSeq: 1 INVITE
User-Agent: RTC/1.2
Content-Length: 0


sipcs: 10:47:03.403 dispatchDE: dlg[358]
sipcs: UK-PEM:HANDLE(NON-CONNECTED):<<EVENT(1)<<DLG[358]
10:47:03.403 +++ CIFace::Event +++
  +++ Pre-event +++
    Type EventRinging
    Devices: <6003/6003> <-/7000> <-/->
    ANI/DNIS: <7000> <6003>
    Flags: divert=0 hook=1 postCall=0 active=1 moveAll=1 callType=1
  --- Pre-event ---
  +++ Ringing +++
    -- created call_info_tspp 0090016ddc31b04d@01C01B60
@10:47:03.4030 Call [0090016ddc31b04d]: urid 00010090
    -- created aTmCall 0181CB38/01C01B60
@10:47:03.4030 [BSYNC] Trace: Send to backup (TServer_SIPPremise_Backup) [404]: message EventUserEvent
attr_#1005 0
attr_#1004 403
attr_#1003 1172713623
attr_#1002 1448
attr_#1001 1
attr_#1000 131072
attr_#15101 77
AttributeUserEvent [15001]

[/color]
[/font]
[/size]
Logged

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: TMonitor and SIP
« Reply #1 on: March 01, 2007, 10:46:15 AM »
Hi Vic,

It's possible to specify monitor mode by attaching the key "MonitorMode" to Extensions Attributes. The possible values are:

normal - a mute connection with possible warning beep
connect - a three-party conference
mute - a mute connection
coach - whisper coaching - only an agent can hear the supervisor

R.
Logged

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Re: TMonitor and SIP
« Reply #2 on: March 02, 2007, 05:12:28 AM »
René!

Here is what worked for me based on what you suggested:

[size=8pt]      [color=green]  private void button1_Click(object sender, EventArgs e)
        {
            DesktopToolkitX.CTKVPair myPair;
            DesktopToolkitX.CTKVList myList;

            //2007/01/25 DBG y.oki
            //string reasonCode=string.Empty;
            this.ReasonCode = string.Empty;


            myPair = new DesktopToolkitX.CTKVPair();
            myList = new DesktopToolkitX.CTKVList();

            myPair.Key = "MonitorMode";
            myPair.Type = DesktopToolkitX.CTKVType.CKVTypeString;
            myPair.StringValue = "mute";
            myList.AddHead(myPair);
            TExtension.TSetExtensions(myList);

            sMonitorNumber = cboDial.Text;

            DesktopToolkitX.TStatus rc =
this.TExtension.TMonitorNextCall(sMonitorNumber, 　　　　　DesktopToolkitX.TMonitorNextCallType.MonitorAllCalls);[/color]
[/size]
        }
Logged

ddeitch

  • Guest
a=rtpmap:101 telephone-event/8000
« Reply #3 on: April 07, 2008, 05:08:34 PM »
what is 101 telephone-event/8000 mean?
Logged
Pages: [1]   Go Up
« previous next »