For example, in this NOTIFY message, in the body I can see 'Event: talk', I assume that the SIP Server would translate this to mean that the agent is busy.
08:18:31.984: Sending [0,UDP] 468 bytes to 10.8.0.3:5060 >>>>>
NOTIFY sip:4000@10.8.0.3:5060 SIP/2.0
From: sip:4001@10.3.1.7:5060;tag=002B50D4-406A-1FAC-BDE5-0701030AAA77-8065
To: <sip:2101@10.3.1.7:5060>;tag=FB85713D-E5CD-4EBD-9E11-282F0EDA48C1-2
Call-ID: 002B50C0-406A-1FAC-BDE5-0701030AAA77-8053@10.3.1.7
CSeq: 2 NOTIFY
Content-Length: 0
Via: SIP/2.0/UDP 10.3.1.7:5060;branch=z9hG4bK002B50D5-406A-1FAC-BDE5-0701030AAA77-8070
Contact: <sip:4001@10.3.1.7:5060>
Event: talk
Subscription-State: active
Max-Forwards: 70
I would like to know what other 'event's would the SIP Server expect to see when an agent goes 'ready' or 'not ready', etc.
There has to be some documentation somewhere that defines the structure/format of the NOTIFY message that the Genesys SIP Server is expecting, such that it understands and can translate that into TLib agent events, ie. EventAgentNotReady.