CN104243290B - A dispatching platform communication method and system based on instant message - Google Patents

Abstract

The invention discloses a communication method for dispatching station based on instant message. By introducing the instant message (Message method) of SIP protocol into the dispatching communication system to realize the real-time communication between the dispatching station and the dispatching server, XML coding is adopted in the message body The real-time instant message transmits the requests, responses and event messages of scheduling business commands, and the immediacy of instant message content transmission can meet the real-time requirements of the system. The invention effectively solves the problems in the prior art that the communication protocol of the dispatching station is privately closed and the service expansion is difficult, thereby increasing the standardization and openness of the system and improving the expansion ability of new services.

Description

A dispatching platform communication method and system based on instant message

technical field

The invention belongs to the technical field of communication, and relates to a communication method of a dispatching station, which uses the instant message of the SIP protocol to transmit the operation request/response of the dispatching station.

Background technique

The dispatching communication system of some industries (such as electric power) generally includes dispatching switches, dispatching consoles, dispatching extensions and other equipment. Among them, the dispatching station, as a client, provides dispatchers at all levels with an operation interface for dispatching telephone operations, and presents the status of dispatching telephones in real time. Multiple dispatching stations form a dispatching station group; ) to provide call control services and events of dispatching extensions for each dispatching console.

In the prior art, the operation requests, responses, and event messages between the dispatcher and the server are generally communicated using proprietary protocols, which makes it difficult to expand services, and it is difficult to analyze the communication messages of the dispatcher during functional testing.

Softswitch technology based on IP network has been greatly developed and applied on a large scale in the communication field. The SIP protocol and its extensions define the establishment, modification and termination of session interaction, which is changing the way people use the Internet to communicate. Message method—SIP extension RFC3428, which allows instant messages to be sent. The most important feature of an instant message system is the immediacy of content delivery, which enables near-real-time information interaction between two or more users.

Contents of the invention

In view of this, the embodiment of the present invention provides a dispatching station communication method based on instant messages, the dispatching station and the dispatching server send instant messages through the Message method of the SIP protocol, and the call operation request and response of the XML code are carried in the message body And event messages, increase the standardization and openness of the system, and improve the expansion capability of new services.

In order to achieve the above purpose, embodiments of the present invention provide the following technical solutions:

The system adopts the soft switch of the current mainstream soft switch equipment manufacturer as the dispatching switch, and the dispatching server is independent of the dispatching switch. Through CSTA/TAPI/TSAPI/JTAPI and other standard CTI protocols, the computer telecommunication application integration with the soft switches of different manufacturers is realized, and it is a dispatching platform. Provides call control services for cross-vendor soft switches. The SIPMessage instant message is sent between the dispatch console and the dispatch server through the SIP server, and the XML (ExtensibleMarkupLanguage) format information of the dispatch operation request, response and/or event message is carried in the message body.

The SIPMessage instant message body starts from the call event <CallEvent> root element, including the message header <MessageHead> element and the event message <EventMessage> element. Among them, the <MessageHead> element of the message header defines the public information of the system message, including the dispatching server identification <AS-ID> element, the dispatching platform identification <DIS-ID> element, the event sequence number <SerialNo> element and the event occurrence time <GeneralizedTime > element; the event message <EventMessage> element selectively includes the call event <CallEvent> element and the operation event <OperateEvent> element according to the value of the event attribute eventtype.

When the value of the event attribute eventtype indicates that the SIPMessage instant message body is an uplink message sent from the dispatch server to the dispatcher, the event message element includes a call event <CallEvent> element, and the uplink message includes a response message for executing the dispatcher's operation request or The monitored call event message of the dispatch phone.

According to the value of the call event attribute CallEventNo, the call event <CallEvent> element in the SIPMessage instant message body includes one or more of the following elements: operation command response <CMDRspEvent> element, call connection state change event <ConnectionStateEvent> element , a forwarding feature setting event <forwardEvent> element, a ringing feature setting event <ringEvent> element, an automatic answering feature setting event <autoAnswerEvent> element and/or a scheduling switch connection event <connectEvent> element.

When the value of the event attribute eventtype indicates that the SIPMessage instant message body is a downlink message sent from the dispatcher console to the dispatcher server, the event message element includes an operation event <OperateEvent> element, and the downlink message includes a dispatcher's dispatch operation request message;

According to the value of the call event attribute CallEventNo, the operation event <OperateEvent> element in the SIPMessage instant message body includes one or more of the following elements: dispatcher registration <DisRegCMD> element, dispatcher cancellation <DisUnRegCMD> element, call Initiate <DisCallStartCMD> element, call answer <DisAnswerCMD> element, call release <DisCallReleaseCMD> element, call hold <DisCallHoldCMD> element, call recovery <DisCallRetriveCMD> element, call blind transfer <DisCallForwardCMD> element, call negotiation <DisConsultationCallCMD> element, call Pickup <DisPickupCallCMD> element, call transfer <DisTransferCallCMD> element, call park <DisParkCallCMD> element, call intrusion <DisCallInsertCMD> element, call force release <DisCallRELCMD> element, conference initiation <DisConfStartCMD> element, conference end <DisConfRelCMD> element, conference control <DisConfCtrlCMD> element, set forwarding <DisSetForwardCMD> element, set ring opening and closing <DisSetRingCMD> element and/or set automatic answer <DisSetAutoanswerCMD> element.

Description of drawings

Fig. 1 is the schematic diagram of the relationship between dispatching platform and dispatching communication system in the embodiment of the present invention, dispatching soft switch, dispatching extension (IP telephone), dispatching server, SIP server;

Fig. 2 is the flow chart of dispatching platform communication service request, response of the embodiment of the present invention;

Fig. 3 is a flow chart of reporting an IP phone event message to a dispatching station according to an embodiment of the present invention.

detailed description

The specific embodiment of the present invention will be further described in detail below in conjunction with the accompanying drawings.

Fig. 1 is a schematic diagram of the relationship between the dispatching console and the dispatching communication system of the embodiment of the present invention, the dispatching soft switch, the dispatching extension (IP phone), the dispatching server, and the SIP server. The SIP protocol stack must be run on the SIP server 10, the dispatching console 20, and the dispatching server 30, and the dispatching console and the dispatching server are all registered on the SIP server by the SIP protocol stack module. Therefore, the system structure includes: the SIP protocol on the SIP server 10 The stack module 101 , the SIP protocol stack module 201 on the dispatching console 20 , and the SIP protocol stack module 301 on the dispatching server 30 .

Fig. 2 is a flow chart of the communication service request and response of the dispatching station of the embodiment. The dispatcher console is the console used by the dispatcher for dispatching telephone operations. The dispatcher sends an operation request to the dispatching server through the function buttons on the interface. The SIP protocol stack module 201 of the dispatcher uses the Message method of the SIP protocol to send the message in the form of a SIPMessage instant message body. Send the request message to the SIP protocol stack module 101 of the SIP server, the SIP protocol stack module 101 sends it to the SIP protocol stack module 301 of the scheduling server immediately after receiving the message, and the SIP protocol stack module 301 immediately responds to the definition in the SIP protocol after receiving the message The 200OK method is given to the SIP protocol stack module 101 of the SIP server to indicate receipt, and the SIP protocol stack module 101 immediately sends to the dispatcher's SIP protocol stack module 201 after receiving the 200OK response to indicate that the dispatcher server receives the operation request. The dispatching server receives the operation requests from all the dispatching stations in the system, executes the dispatching strategy, requests the dispatching switch to perform the corresponding call control service through standard CTI protocols such as CSTA, and generates an operation command response message after receiving the response from the dispatching switch and sends it to the requesting party Dispatch console, the SIP protocol stack module 301 of dispatch server uses the Message method of SIP agreement to send response message to the SIP protocol stack module 101 of SIP server, and SIP protocol stack module 101 sends to the SIP protocol stack module of dispatch console immediately after receiving the message 201, the SIP protocol stack module 201 immediately responds with 200 OK to the SIP protocol stack module 101 of the SIP server after receiving the message to indicate receipt, and the SIP protocol stack module 101 immediately sends it to the SIP protocol stack module 301 of the scheduling server after receiving the 200 OK response to indicate scheduling The station receives a response message. Table 1 provides the definition of operation command request and response. The SIPMessage instant message body starts from the call event <CallEvent> root element, including the message header <MessageHead> element and the event message <EventMessage> element.

The message header <MessageHead> element defines the public information of the system message, including the scheduling server identification <AS-ID> element, the dispatching platform identification <DIS-ID> element, the event sequence number <SerialNo> element and the event occurrence time <GeneralizedTime> element ; The event message <EventMessage> element selectively includes a call event <CallEvent> element and an operation event <OperateEvent> element according to the value of the event attribute eventtype. When the value of the event attribute eventtype indicates that the SIPMessage instant message body is an uplink message sent from the dispatch server to the dispatcher, the event message element includes a call event <CallEvent> element, and the uplink message includes a response message for executing the dispatcher's operation request or The monitored call event message of the dispatch phone.

According to the value of the call event attribute CallEventNo, the call event <CallEvent> element in the SIPMessage instant message body includes one or more of the following elements: operation command response <CMDRspEvent> element, call connection state change event <ConnectionStateEvent> element , a forwarding feature setting event <forwardEvent> element, a ringing feature setting event <ringEvent> element, an automatic answering feature setting event <autoAnswerEvent> element and/or a scheduling switch connection event <connectEvent> element.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a response message to the dispatcher's operation request, the call event <CallEvent> element in the SIPMessage instant message body contains an operation command response <CMDRspEvent> element, which further includes Dispatcher console number, operation command number, operation response result and conference ID returned when initiating a conference operation;

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call connection state change event of the monitored dispatching phone, the call event <CallEvent> element in the SIPMessage instant message body contains the call connection state change event <ConnectionStateEvent >Elements, which further include device monitoring identifier, device number, call identifier, outgoing call identifier, conference call, event identifier, event time, time type, connection status and status change reason;

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is the forwarding feature setting event of the monitored dispatch phone, the call event <CallEvent> element in the SIPMessage instant message body contains the forwarding feature setting event <forwardEvent > element, which further includes equipment number, forwarded target number, forwarded type and forwarded state;

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is an event for setting the ring feature of the monitored dispatch phone, the call event <CallEvent> element in the SIPMessage instant message body contains the feature set event for ring event <ringEvent > element, which further contains device number and bell on/off status;

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is the automatic answering feature setting event element of the monitored dispatch phone, the call event <CallEvent> element in the SIPMessage instant message body contains the automatic answering feature setting event< autoAnswerEvent> element, which further includes device number, auto-answer status and number of rings;

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is the dispatching switch connection event of the monitored dispatching phone, the call event <CallEvent> element in the SIPMessage instant message body contains the dispatching switch connection event <connectEvent> element , which further includes a connection type and a connection state.

When the value of the event attribute eventtype indicates that the SIPMessage instant message body is a downlink message sent from the dispatcher console to the dispatcher server, the event message element in the SIPMessage instant message body includes an operation event <OperateEvent> element, and the downlink message includes the dispatcher's Scheduling operation request message;

According to the value of the call event attribute CallEventNo, the operation event <OperateEvent> element in the SIPMessage instant message body includes one or more of the following elements: dispatcher registration <DisRegCMD> element, dispatcher cancellation <DisUnRegCMD> element, call Initiate <DisCallStartCMD> element, call answer <DisAnswerCMD> element, call release <DisCallReleaseCMD> element, call hold <DisCallHoldCMD> element, call recovery <DisCallRetriveCMD> element, call blind transfer <DisCallForwardCMD> element, call negotiation <DisConsultationCallCMD> element, call Pickup <DisPickupCallCMD> element, call transfer <DisTransferCallCMD> element, call park <DisParkCallCMD> element, call intrusion <DisCallInsertCMD> element, call force release <DisCallRELCMD> element, conference initiation <DisConfStartCMD> element, conference end <DisConfRelCMD> element, conference control <DisConfCtrlCMD> element, set forwarding <DisSetForwardCMD> element, set ring opening and closing <DisSetRingCMD> element and/or set automatic answer <DisSetAutoanswerCMD> element.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a registration operation request to the dispatcher, the operation event <OperateEvent> element in the SIPMessage instant message body contains the dispatcher registration <DisRegCMD> element, which further includes the dispatcher Left handle number, dispatcher right handle number, dispatcher group number, dispatcher group emergency number and registration time.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a logout operation request to the dispatcher, the operation event <OperateEvent> element in the SIPMessage instant message body includes the dispatcher logout <DisUnRegCMD> element, which further includes the dispatcher Left handle number, dispatcher right handle number, dispatcher group number, dispatcher group emergency number and logout time.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call initiation request to the dispatcher console, the operation event <OperateEvent> element in the SIPMessage instant message body contains the call initiation <DisCallStartCMD> element, which further includes the dispatcher console handle number, called number and call time.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call response request to the dispatcher console, the operation event <OperateEvent> element in the SIPMessage instant message body contains the call response <DisAnswerCMD> element, which further includes the dispatcher console handle number, call identification, calling number, and answer time.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call release request to the dispatcher console, the operation event <OperateEvent> element in the SIPMessage instant message body contains the call release <DisCallReleaseCMD> element, which further includes the dispatcher console handle Number, Call ID, Subscriber Number and Release Time.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call hold request to the dispatcher console, the operation event <OperateEvent> element in the SIPMessage instant message body contains the call hold <DisCallHoldCMD> element, which further includes the dispatcher console handle number, call ID, and number of held calls.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call recovery request to the dispatcher, the operation event <OperateEvent> element in the SIPMessage instant message body contains a call recovery <DisCallRetriveCMD> element, which further includes the dispatcher handle number, call ID, and number from which the call was retrieved.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call blind transfer request to the dispatcher, the operation event <OperateEvent> element in the SIPMessage instant message body includes a call blind transfer <DisCallForwardCMD> element, which further includes a dispatcher Handset number, call ID, calling number and transfer destination number.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call negotiation request to the dispatcher, the operation event <OperateEvent> element in the SIPMessage instant message body contains the call negotiation <DisConsultationCallCMD> element, which further includes the dispatcher handle number, call identification, telephone number to call another party and consult.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call pickup request to the dispatcher, the operation event <OperateEvent> element in the SIPMessage instant message body includes a call pickup <DisPickupCallCMD> element, which further includes a dispatcher The handset number, the device to be picked up and the call to be picked up.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call transfer request to the dispatcher, the operation event <OperateEvent> element in the SIPMessage instant message body includes a call transfer <DisTransferCallCMD> element, which further includes a dispatcher phone number, primary call ID and secondary call ID.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call park request to the dispatcher, the operation event <OperateEvent> element in the SIPMessage instant message body includes a call park <DisParkCallCMD> element, which further includes a dispatcher phone number, call ID, caller and parked phone number.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call insertion request to the dispatcher, the operation event <OperateEvent> element in the SIPMessage instant message body includes a call insertion <DisCallInsertCMD> element, which further includes a dispatcher The handset number, the call ID of the handset, the call ID of the call to be inserted, and the calling/called number to be inserted.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a call forced release request to the dispatcher console, the operation event <OperateEvent> element in the SIPMessage instant message body contains the call forced release <DisCallRELCMD> element, which further includes the dispatcher console handle number, the call ID to be plugged and removed, and the user number to make a call.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a conference initiation request, the operation event <OperateEvent> element in the SIPMessage instant message body includes the conference initiation <DisConfStartCMD> element, which further includes the conference group number, scheduling Handle number, conference call ID, conference type, reason, number of conference members, conference start time and conference duration.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a conference end request, the operation event <OperateEvent> element in the SIPMessage instant message body includes the conference end <DisConfRelCMD> element, which further includes the conference group number, scheduling Handle number, conference call ID, conference type, reason, number of conference members, conference start time and conference duration.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a conference control request, the operation event <OperateEvent> element in the SIPMessage instant message body includes a conference control <DisConfCtrlCMD> element, which further includes the dispatcher handle number, conference Call ID, conference opcode, conference members, and resource names.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a forwarding request, the operation event <OperateEvent> element in the SIPMessage instant message body contains a set forwarding <DisSetForwardCMD> element, which further includes the dispatcher handle number , forwarded destination number and forwarded type.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a request to set the ring opening and closing ring, the operation event <OperateEvent> element in the SIPMessage instant message body includes setting the ring opening and closing ring <DisSetRingCMD> element, which further includes Dispatcher console number and bell on/off status.

When the value of the call event attribute CallEventNo indicates that the SIPMessage instant message body is a request for setting an automatic answer, the operation event <OperateEvent> element in the SIPMessage instant message body contains an element for setting an automatic answer <DisSetAutoanswerCMD>, which further includes the dispatcher handle number , auto answer status and the number of rings.

Table 1 Operation Command Request and Response

Fig. 3 is a flow chart of reporting an IP phone event message to a dispatching station in an embodiment. The dispatching server monitors the events generated by the dispatching phone during the entire call process through standard CTI protocols such as CSTA, and sends them to all dispatching stations including the user on the dispatching station interface. The SIP protocol stack module 301 of the dispatching server uses the Message method of the SIP protocol , send the call event to the SIP protocol stack module 101 of the SIP server in the form of a SIPMessage instant message body, the SIP protocol stack module 101 sends the message to the SIP protocol stack module 201 of the target dispatcher immediately after receiving the message, and the SIP protocol stack module 201 receives the message Respond 200OK to the SIP protocol stack module 101 of SIP server immediately after the message and represent receipt, and the SIP protocol stack module 301 that the SIP protocol stack module 101 sends to the dispatching server immediately after receiving the 200OK response indicates that the dispatcher receives the call event message, each The dispatcher handles the received call event, and the call status of the dispatcher phone is indicated by the color of the button on the interface. Definitions of call events are provided in Table 2.

Form 2 call event

The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (12)

1. a dispatching station communication method based on instant message in dispatching communication system, this dispatching communication system comprises dispatching soft switch, dispatching extension, dispatching server, SIP server and dispatching station, it is characterized in that: comprise the steps: SIPMessage instant messages are sent between the dispatching station and the dispatching server through the SIP server; The dispatching server integrates with the computer telecommunication application of the dispatching soft switch through the CTI protocol, and provides the dispatching station with the call control service of the cross-manufacturer dispatching soft switch. Wherein the SIPMessage instant message carries scheduling operation request message, response message and/or event message in XML format; Wherein the step of sending the SIPMessage instant message through the SIP server between the dispatching platform and the dispatching server comprises: The dispatcher sends the dispatch operation request message to the SIP server in the form of a SIPMessage instant message; After the SIP server receives the scheduling operation request message, it sends it to the scheduling server; After the scheduling server receives the scheduling operation request message, it responds to the SIP server with 200 OK defined in the SIP protocol to indicate receipt; After the SIP server receives the 200OK response, it sends it to the dispatching console to indicate that the dispatching server has received the dispatching operation request. 2. The method according to claim 1, characterized in that: the step of sending a SIPMessage instant message through a SIP server between the dispatching console and the dispatching server comprises: The dispatching server monitors the events generated by the dispatching phone during the entire call process through standard CTI protocols such as CSTA; The scheduling server sends the call event message to the SIP server in the form of a SIPMessage instant message; After receiving the call event message, the SIP server sends it to the target dispatcher immediately; After receiving the call event message, the target dispatcher immediately responds with 200 OK to the SIP server to indicate receipt; After receiving the 200OK response, the SIP server immediately sends it to the dispatch server to indicate that the dispatch console has received the call event message; Each dispatcher handles the received call events, and the call status of the dispatcher phone is indicated by the color of the button on the interface. 3. The method according to claim 1, characterized in that: wherein said dispatching server is integrated with the computer telecommunication application of the dispatching soft switch by the CTI protocol, and the step of providing the call control service of the cross-manufacturer soft switch for the dispatching station comprises: The dispatching server receives dispatching operation requests from all dispatching stations in the system, executes dispatching strategies, and requests dispatching soft switches to perform corresponding call control services through the CTI protocol. 4. The method according to claim 1, wherein the SIPMessage instant message starts from the call event <CallEvent> root element, including a message header <MessageHead> element and an event message <EventMessage> element, wherein, The message header <MessageHead> element defines the public information of the system message, including the scheduling server identification <AS-ID> element, the dispatching platform identification <DIS-ID> element, the event sequence number <SerialNo> element and the event occurrence time <GeneralizedTime> element ; The event message <EventMessage> element includes a call event <CallEvent> element or an operation event <OperateEvent> element according to the value of the event attribute eventtype, Wherein, when the value of the event attribute eventtype indicates that the SIPMessage instant message is an uplink message sent from the dispatch server to the dispatcher, the event message element includes a call event <CallEvent> element, and the uplink message includes a response message for executing the dispatcher's operation request or the monitored call event message of the dispatch phone; According to the value of the call event attribute CallEventNo, the call event <CallEvent> element in the SIPMessage instant message includes one or more of the following elements: an operation command response <CMDRspEvent> element, a call connection state change event <ConnectionStateEvent> element, Forwarding feature setting event <forwardEvent> element, ring opening feature setting event <ringEvent> element, automatic answering feature setting event <autoAnswerEvent> element and/or scheduling soft switch connection event <connectEvent> element. 5. The method according to claim 4, wherein, when the value of the event attribute eventtype indicates that the SIPMessage instant message is a downlink message sent from the dispatch console to the dispatch server, the event message element includes an operation event <OperateEvent> element, the downlink message includes a dispatcher's dispatch operation request message; According to the value of the call event attribute CallEventNo, the operation event <OperateEvent> element in the SIPMessage instant message includes one or more of the following elements: dispatcher registration <DisRegCMD> element, dispatcher cancellation <DisUnRegCMD> element, call initiation <DisCallStartCMD> element, call answer <DisAnswerCMD> element, call release <DisCallReleaseCMD> element, call hold <DisCallHoldCMD> element, call recovery <DisCallRetriveCMD> element, call blind transfer <DisCallForwardCMD> element, call negotiation <DisConsultationCallCMD> element, call agent Pickup <DisPickupCallCMD> element, call transfer <DisTransferCallCMD> element, call park <DisParkCallCMD> element, call intrusion <DisCallInsertCMD> element, call force release <DisCallRELCMD> element, conference initiation <DisConfStartCMD> element, conference end <DisConfRelCMD> element , conference control <DisConfCtrlCMD> element, set forwarding <DisSetForwardCMD> element, set ring opening and closing <DisSetRingCMD> element and/or set automatic answer <DisSetAutoanswerCMD> element. 6. A dispatching communication system, the system includes a dispatching soft switch, a dispatching extension, a dispatching server, a SIP server and a dispatching console, characterized in that: There are SIP protocol stack modules on the SIP server, dispatching console and dispatching server respectively; The SIP protocol stack module of the dispatching console and the dispatching server sends the SIPMessage instant message through the SIP protocol stack module of the SIP server; The dispatching server integrates with the computer telecommunication application of the dispatching soft switch through the CTI protocol, and provides the dispatching station with the call control service of the cross-manufacturer dispatching soft switch. The SIPMessage instant message carries information in XML format of scheduling operation request message, response message and/or event message. 7. system as claimed in claim 6, wherein between the SIP protocol stack module of said dispatcher and dispatch server, send SIPMessage instant message by the SIP protocol stack module of SIP server, it is characterized in that: comprise: The dispatcher sends the dispatch operation request message to the SIP server in the form of a SIPMessage instant message; After the SIP server receives the scheduling operation request message, it sends it to the scheduling server; After the scheduling server receives the scheduling operation request message, it responds to the SIP server with 200 OK defined in the SIP protocol to indicate receipt; After the SIP server receives the 200OK response, it sends it to the dispatching console to indicate that the dispatching server has received the dispatching operation request. 8. The system according to claim 6, wherein the SIPMessage instant message is sent by a SIP server between the dispatching console and the dispatching server, characterized in that: comprising: The dispatching server monitors the events generated by the dispatching phone during the entire call process through standard CTI protocols such as CSTA; The scheduling server sends the call event message to the SIP server in the form of a SIPMessage instant message; After receiving the call event message, the SIP server sends it to the target dispatcher immediately; After receiving the call event message, the target dispatcher immediately responds with 200 OK to the SIP server to indicate receipt; After receiving the 200OK response, the SIP server immediately sends it to the dispatch server to indicate that the dispatch console has received the call event message; Each dispatcher handles the received call events, and the call status of the dispatcher phone is indicated by the color of the button on the interface; Wherein the dispatching server realizes the computer telecommunication application integration with the dispatching soft switch through the CTI protocol, and provides the call control service of the cross-manufacturer soft switch for the dispatching station, including: The dispatching server receives dispatching operation requests from all dispatching stations in the system, executes dispatching strategies, and requests dispatching soft switches to perform corresponding call control services through the CTI protocol. 9. The system according to claim 6, wherein the CTI protocol is one and/or more of CSTA, TAPI, TSAPI, and JTAPI standards, wherein the SIPMessage instant message starts from the call event <CallEvent> root element, Including message header <MessageHead> element and event message <EventMessage> element; among them, The message header <MessageHead> element defines the public information of the system message, including the scheduling server identification <AS-ID> element, the dispatching platform identification <DIS-ID> element, the event sequence number <SerialNo> element and the event occurrence time <GeneralizedTime> element ; The event message <EventMessage> element includes a call event <CallEvent> element or an operation event <OperateEvent> element according to the value of the event attribute eventtype, Wherein, when the value of the event attribute eventtype indicates that the SIPMessage instant message is an uplink message sent from the dispatch server to the dispatcher, the event message element includes a call event <CallEvent> element, and the uplink message includes a response message for executing the dispatcher's operation request or the monitored call event message of the dispatch phone; According to the value of the call event attribute CallEventNo, the call event <CallEvent> element in the SIPMessage instant message includes one or more of the following elements: an operation command response <CMDRspEvent> element, a call connection state change event <ConnectionStateEvent> element, Forwarding feature setting event <forwardEvent> element, ring opening feature setting event <ringEvent> element, automatic answering feature setting event <autoAnswerEvent> element and/or scheduling soft switch connection event <connectEvent> element. 10. The system according to claim 9, wherein, when the value of the event attribute eventtype indicates that the SIPMessage instant message is a downlink message sent from the dispatch console to the dispatch server, the event message element includes an operation event <OperateEvent> element, the downlink message includes a dispatcher's dispatch operation request message; According to the value of the call event attribute CallEventNo, the operation event <OperateEvent> element in the SIPMessage instant message includes one or more of the following elements: dispatcher registration <DisRegCMD> element, dispatcher cancellation <DisUnRegCMD> element, call initiation <DisCallStartCMD> element, call answer <DisAnswerCMD> element, call release <DisCallReleaseCMD> element, call hold <DisCallHoldCMD> element, call recovery <DisCallRetriveCMD> element, call blind transfer <DisCallForwardCMD> element, call negotiation <DisConsultationCallCMD> element, call agent Pick up <DisPickupCallCMD> element, call transfer <DisTransferCallCMD> element, call park <DisParkCallCMD> element, call intrusion <DisCallInsertCMD> element, call force release <DisCallRELCMD> element, conference initiation <DisConfStartCMD> element, conference end <DisConfRelCMD> element , conference control <DisConfCtrlCMD> element, set forwarding <DisSetForwardCMD> element, set ring opening and closing <DisSetRingCMD> element and/or set automatic answer <DisSetAutoanswerCMD> element. 11. A dispatching communication system based on instant message execution dispatching station communication method, this system comprises dispatching soft switch, dispatching extension, dispatching server, SIP server and dispatching station, it is characterized in that: The dispatcher is configured to send the dispatch operation request message to the SIP server in the form of a SIPMessage instant message; The SIP server is configured to send to the scheduling server after receiving the scheduling operation request message; The scheduling server is configured to respond to the SIP server with 200 OK defined in the SIP protocol after receiving the scheduling operation request message; The SIP server is also used to send it to the dispatcher to indicate that the dispatcher receives the dispatch operation request after receiving the 200OK response; The dispatching server receives dispatching operation requests from all dispatching stations in the system, executes the dispatching strategy, and requests the dispatching soft switch to execute the corresponding call control service through the CTI protocol. 12. A dispatching communication system based on instant message execution dispatching station communication method, this system comprises dispatching soft switch, dispatching extension, dispatching server, SIP server and dispatching station, it is characterized in that: The scheduling server is used to monitor the events generated by the scheduling phone during the entire call process through standard CTI protocols such as CSTA, and send the call event message to the SIP server in the form of a SIPMessage instant message; SIP server is used for sending to the target dispatcher immediately after receiving the call event message; The target dispatcher is used to respond 200 OK to the SIP server to indicate receipt immediately after receiving the call event message; The SIP server is also used to send to the dispatch server immediately after receiving the 200OK response to indicate that the dispatch station receives the call event message; Each target dispatching station is also used to process the received call event, and the call status of the dispatching phone is indicated by the color of the button on the interface.