I have two SIP servers. SIP A has agents and SIP B has a RP on which strategy is loaded which sends the calls to agents on the other SIP server.
For what you describe you did all what you need. Does Sip1 can call sip2 ERP?
And what is the problem you are facing? Logs desirable
ill share logs shortly, but do u need access codes in these cases and also trunks? if yes please describe how?
It depends on what ISCC type you want to use. In almost scenarios is the “route” or “direct-uui” type used. If there is no special requirement to have the “route” type, I recommend to use “direct-uui” which does not need the ERP at all. In this case, you just have to create the trunks (tieline) on each site pointing to each other, configure access codes.
I just want all the data from one switch to be transferred to the other switch along with the calls should come to agents on the other switch.
in trunks, prefix is necessary? how to configure access codes
Did you read the documentation anytime? Try to follow it, please - all is described very well. Prefix is recommended - same as the access code uses.
And also, we discussed that just a while ago on another post. Please search
hey guys the thing is that in routing sip server i am receving this erro:
Line 840: @02:48:38.0780 [ISCC] Error: Server SIP_Server@SIP_Switch/1 has rejected the connection. Reconnecting…
this is received again
and in URS logs I can see it saying the target agent is invalid. This could be the reason, but how to get connected to the agent sip server. its like completing the handshake. please help guys
Post logs!
This happens again. What does this mean AND how should I solve this. I think that is why URS is not considering the agents as valid
Line 466: @18:28:47.7250 [ISCC] [connection 0000000002a41810] Starting connection [628]1
Line 467: @18:28:47.7250 [ISCC] [connection 0000000002a41810] Parameters: (“name”=“SIP_Server”,“host”=“demosrv.genesyslab.com”,“is-server”=“1”,“client-type”=“1”,“server-type”=“1”,“port”=“7004”,“protocol”=“addp”,“addp-timeout”=“0”,“addp-remote-timeout”=“0”,“addp-trace”=“both”)
Line 470: @18:28:47.7250 [ISCC] [connection 0000000002a41810] Socket connected on connection [628]1
Line 471: @18:28:47.7250 [ISCC] {server SIP_Server@SIP_Switch {role backup} {authorizing}}
Line 472: @18:28:47.7250 [ISCC] Send to server SIP_Server@SIP_Switch/1: message ISCCRequestAuthorize
Line 472: @18:28:47.7250 [ISCC] Send to server SIP_Server@SIP_Switch/1: message ISCCRequestAuthorize
Line 473: ISCCAttributeTrackingID 6619138 [00650002]
Line 474: ISCCAttributeReferenceID 6619138 [00650002]
Line 475: ISCCAttributeTSCPVersion ‘8.1.000.25’
Line 476: ISCCAttributeServerVersion ‘8.1.000.44’
Line 477: ISCCAttributeServerXCapabilities ‘(2=(56=396273),8=(16=7),10=(16=15),11=(16=25),14=(73=1),34=(67=3),36=(60=131),75=(16=1),76=(16=25),108=(74=2),113=(83=132604),160=(146=1),161=(146=1),162=(146=1))’
Line 478: ISCCAttributeServerCapabilityMask {bstring}
Line 479: ISCCAttributeProtocolVersion ‘ISCC protocol 5.1’
Line 479: ISCCAttributeProtocolVersion ‘ISCC protocol 5.1’
Line 480: ISCCAttributeDeviceType -1 [ffffffff]
Line 481: ISCCAttributeServerRole Primary
Line 482: ISCCAttributeServerLocation ‘VM-SIPServer-Switch’
Line 483: ISCCAttributeServerName ‘VM-SIPServer’
Line 484: @18:28:47.7250 [ISCC] [connection 0000000002a41810] Sent to connection [628]2
Line 486: @18:28:47.7270 [ISCC] [connection 0000000002a41810] Received from connection [628]2
Line 487: @18:28:47.7270 [ISCC] Received from server SIP_Server@SIP_Switch/1: message ISCCEventAuthorizeResponse
Line 487: @18:28:47.7270 [ISCC] Received from server SIP_Server@SIP_Switch/1: message ISCCEventAuthorizeResponse
Line 488: ISCCAttributeResponseCode Not_Configured
Line 489: ISCCAttributeReferenceID 6619138 [00650002]
Line 490: ISCCAttributeTrackingID 6553605 [00640005]
Line 491: @18:28:47.7270 [ISCC] Error: Server SIP_Server@SIP_Switch/1 has rejected the connection. Reconnecting…
Line 492: @18:28:47.7270 [ISCC] [connection 0000000002a41810] disconnected [628]2
Line 493: @18:28:47.7270 [ISCC] {server SIP_Server@SIP_Switch {role backup} {disconnected}}
Line 494: @18:28:47.7270 [ISCC] {server SIP_Server@SIP_Switch {role backup} {connecting}}
Line 495: @18:28:47.7270 [ISCC] [connection 0000000002a41810] connecting [0]1
just to elaborate SIP_Server@SIP_Switch is the target tserver were the agents reside
You can solve it by learning how Genesys works, about the event model and by reading the documentation, where the entire approach with deep details is described very well. Your configuration seems to be wrong.
Thanks Kubig, I was able to establish the connection and can see the call going into strategy. My strategy is simple with entry->target selection(Agent Group)-> exit. But it gets stuck in the target selection block and doesn’t exit meaning agent doesn’t get the call. URS showing . SNippet of URS logs:
M_I_00650275aa21b002 [10:0c] tenant Environment Agent SM4: dn 7017(ready since 1449198781) is OK
_M_I_00650275aa21b002 [17:0b] VQ 0000000003e28970 Target “QA_SM_SIP_AG”(0000000003dd0290) Component #4 SM4: statvalues: (0)0, 0 1449198781 8519(S) the best
_M_I_00650275aa21b002 [17:0b] VQ 0000000003e28970 Target “QA_SM_SIP_AG”(0000000003dd0290): Component SM4 was SELECTED
_M_I_00650275aa21b002 [17:0e] VQ 0000000003e28970 Target “QA_SM_SIP_AG”(0000000003dd0290): statvalue: (0)0, 2.19733268227e-007(N) the best
_M_I_00650275aa21b002 [17:0e] VQ 0000000003e28970 (virtual queue “VQ_SKY_VM-SIPServer-Switch” id=4): Target “QA_SM_SIP_AG”(0000000003dd0290) for route was SELECTED
_M_I_00650275aa21b002 [01:0d] attempt to route (1)
19:13:29.782_T_E_ [14:0c] EventError is received for tserver VM-SIPServer[VM-SIPServer-Switch] - Invalid Called Dn
19:13:29.782_A_E_00650275aa21b002 [14:32] <-----------ERROR
19:13:29.782 Std 21003 interaction 00650275aa21b002 routing error 0071 Invalid Called Dn
19:13:29.782_M_I_00650275aa21b002 [17:11] VQ 0000000003e28970 first available call: 00650275aa21b002, reason=strategy
_T_W_00650275aa21b002 [0E:0f] emergency: delete call due to this error
19:13:29.782_T_I_00650275aa21b002 [14:02] sending event 58 for virtual queue VQ_SKY_VM-SIPServer-Switch
It is necessary to find out the root cause of the error, from posted fragment this is not possible. Needs little bit more effort.
Okay ill try to do that, can you please guide me how to configure trunks between the twp SIp servers for XRP?
I mean what would be the contact and prefix? i dont understand that
Really? Contact is what sip tells where to call. Ip address and port
Prefix is that, when starting with which numbers should be called that ip address and port
Thanks. Can you please tell would we need to mention the Access code of ERP in the prefix of a trunk made on the routing SIP switch, assuming the ERP is on the other SIP switch
What do you still mention the ERP? Do you want them? I think no… The prefix on trunk level has to be equal to Access Code number.
If you read the documentation, you will understand what you doing and what is the meaning of the mentioned options.