Recently, I feel that the docking seat system is true. First, I chose a fusion network, and then I felt that the function and scope of use were slightly less influential, and then I chose this Tianrun. From a personal point of view, they float. The following is the basic process of recording agent docking.
The docking of the agent system is divided into AXB and clink. This is just for the one I'm currently docking with. Other modes may vary.
1. AXB, this model should be a model for all seat products, A is the seat, X is the trumpet, and B is the customer. In fact, this AXB will change according to different services. The most common one is the one mentioned above. If it is a little more complicated, when we need to make a call to the user, if the user shows that the caller number is the local mobile phone number, then the above is not correct. This kind of In this case, we need to use the agent to bind the fixed-line number first. This fixed-line number is provided by the agent system and can be said to be indispensable. You do not need to connect with this binding. The other party will give you the number of seats and fixed-line number. You can pair them by yourself, write them in the database or enumerate them, use the fixed-line number corresponding to agent A, the mobile phone number of the user to be displayed in X, and the mobile phone number of user B, these three call the AXB interface to bind OK. If the X number is to be obtained automatically according to different regions, you need to pass the attribution of a customer's mobile phone number. This can be requested from an internal relationship, otherwise it will be useless. There is also an outbound call after AXB is bound. If the call is successful, there is an unbinding, which is related to the current agent and the bound X. They have automatic unbinding. After your call is successful, they will automatically unbind your agent from X. The purpose of binding is to save AX resources, but it does not affect the binding relationship between users and X.
Another function of AXB is to call back. I just said that the unbinding of AX does not affect the relationship of XB, so the callback is to use the binding relationship of XB. Not much to say, as long as the above is understood in place, it is natural and clear, the words above are pearly, and there is no nonsense, so be careful.
2. clink, in fact, with the binding relationship of AXB, what Clink mainly does is the action of outbound calls and our business. What should we do if we use this relationship to make calls? It is to use clink for outgoing calls. Of course, outgoing calls are not finished by just calling the outgoing interface. He also has on-line and off-line. Whether to judge online. Then call out. Outgoing calls will have a successful uniqueid for hanging up. The uniqueid will only be available after the synchronous outbound call is successful. In my opinion, this can only be used for synchronization. You basically don't need to do other actions when you make an outbound call. Asynchronous processing of outbound calls is basically useless. Unless, of course, you still want to send a text message.
Then there is the call record, which is simple. basically that's it