" /> SIP Server- Call Not routing - Genesys CTI User Forum

Author Topic: SIP Server- Call Not routing  (Read 6027 times)

Offline tejal

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
SIP Server- Call Not routing
« on: February 23, 2010, 06:03:51 AM »
Advertisement
Hi,
We are setting up a Lab Environment for SIP where we are having issue routing the call.

Im installing it for the first time as a standalone one .
1)I have installed Genesys SIP Server 8 and the other framework components are 7.6.
2)All the DN/Agent Login/Route point configurations has been done as its given in the 8.0 SIP Deployment guide.
3)We are using XLite as the customer phone and logging the agent with Genesys Starter App.
4)Below im explaining the test case executed and the actual error we are getting.

Test Case 1 ( Executed time 4:16 PM IST)
1) Logging in to xlite(IP) phone with user 3000 (Customer)
2) Logging in agent 2000 at Extension 3001 in Genesys Starter App(Who has the right skill for routing)
3) Logging in Agent 2001 at Extension 3003, which Is aet as a default dn.
4) From xlite dialing the route point 4000 where the SIP_ROUITNG_LAB strategy is loaded to route to the particular skill.
5) Xlite shows ringing but does not reach the agent 2000. Neither does it default route to the 3003(Default DN ).

Once tracing the URS logs we see the following

1)      16:15:56.627_T_I_0fc801c76b5470d0 [14:0c] EventRouteRequest is received for tserver SIP_TServer[SIP] (this dn=4000)
9)     _T_I_0fc801c76b5470d0 [14:09] add DN SIP_TServer 4000 <4000@SIP> (CDN 71 0fc801c76b5470d0) to the call 4-01d314c0 truly:11
10)     _T_I_0fc801c76b5470d0 [14:08] check delayed proc
11)     _I_I_0fc801c76b5470d0 [14:33] strategy: *0x65*SIP_ROUTING_LAB is attached to the call
12) 16:15:56.627 Int 20001 interaction 0fc801c76b5470d0 is started
13)     _I_I_0fc801c76b5470d0 [01:14] current call classification: media=voice(100), service=default(200), segment=default(300)
14) 16:15:56.627_I_I_0fc801c76b5470d0 [09:06] >>>>>>>>>>>>start interpretator
15)     _I_I_0fc801c76b5470d0 [09:04] ASSIGN: __Return(SCRIPT) <- STRING:
16)     _I_I_0fc801c76b5470d0 [07:46] no error mode for this call
17)     _I_I_0fc801c76b5470d0 [09:04] ASSIGN: __Return(SCRIPT) <- STRING:
18)     _I_I_0fc801c76b5470d0 [09:04] ASSIGN: __DBReturn(SCRIPT) <- STRING:
19)     _I_I_0fc801c76b5470d0 [09:04] ASSIGN: __DBStrReturn(SCRIPT) <- STRING:
20)     _I_I_0fc801c76b5470d0 [09:04] ASSIGN: __TargetVar(SCRIPT) <- STRING:
21)     _I_I_0fc801c76b5470d0 [07:14] expression translating: Test_Skill <= 5 -> Test_Skill <= 5
22) 16:15:56.627_I_I_0fc801c76b5470d0 [07:07] HERE IS TARGETS
23) TARGETS: ?:Test_Skill <= 5@Stat_Server_761.GA 2000@Stat_Server_761.A
24) 16:15:56.627_M_I_ [17:0c] VQ 01d39f60 created: type=0, tenant=Resources


2)      The Agent 2000 is ready and it throws an Error “Unsupported Operation” from SIP TServer
16:15:56.627_M_I_0fc801c76b5470d0 [17:0e] VQ 01d39f60 (virtual queue "", id=4), (2 Targets): SELECT MAX by statistic <StatTimeInReadyState>(random  )
    _M_I_0fc801c76b5470d0 [17:0b] VQ 01d39f60 Target "?:Test_Skill <= 5"(01d34370) #1, (6-5 Components): SELECT MAX by statistic <StatTimeInReadyState>(random ): MEM(0 1071) 0 0
    _M_I_0fc801c76b5470d0 [17:0b] VQ 01d39f60 Target "?:Test_Skill <= 5"(01d34370) Component #1 2001: logged out
    _M_I_0fc801c76b5470d0 [17:0b] VQ 01d39f60 Target "?:Test_Skill <= 5"(01d34370) Component #2 22222: logged out
    _M_I_0fc801c76b5470d0 [17:0b] VQ 01d39f60 Target "?:Test_Skill <= 5"(01d34370) Component #3 2000: not ready
    _M_I_0fc801c76b5470d0 [17:0b] VQ 01d39f60 Target "?:Test_Skill <= 5"(01d34370) Component #4 222575: logged out
    _M_I_0fc801c76b5470d0 [17:0b] VQ 01d39f60 Target "?:Test_Skill <= 5"(01d34370) Component #5 222574: logged out
    _M_I_0fc801c76b5470d0 [17:0b] VQ 01d39f60 Target "?:Test_Skill <= 5"(01d34370) Component #6 201094: logged out
    _M_I_0fc801c76b5470d0 [17:0b] VQ 01d39f60 Target "?:Test_Skill <= 5"(01d34370): Component for routing was NOT SELECTED (5 1 0 0)
    _M_I_0fc801c76b5470d0 [17:0e] VQ 01d39f60 Target "?:Test_Skill <= 5"(01d34370): not ready passed
    _M_I_0fc801c76b5470d0 [17:0e] VQ 01d39f60 Target "2000"(01d32bb0): not ready passed
    _M_I_0fc801c76b5470d0 [17:0e] VQ 01d39f60 (virtual queue "" id=4): Target for routing was NOT SELECTED (0 0 1 1 0)
    _I_I_0fc801c76b5470d0 [07:0a] HERE IS WAIT (-1 sec)
    _I_I_0fc801c76b5470d0 [07:0a] HERE IS WAIT (10 sec)
16:15:56.627_B_I_0fc801c76b5470d0 [07:0a] delay treatments for 0 msec
16:15:56.627_I_I_0fc801c76b5470d0 [09:04] <<<<<<<<<<<<suspend interpretator(WAIT), timers:11000
16:15:56.627_B_I_0fc801c76b5470d0 [07:09] start chain of treatments
received from 65200(SIP_TServer)CTSINGVCJPAB:7010(fd=) message EventError
(Unsupported operation)
AttributeClientID 4
AttributeThisDN '4000'
AttributeConnID 0fc801c76b5470d0
AttributeReferenceID 23
AttributeErrorMessage 'Unsupported operation'
AttributeErrorCode 51
AttributeTimeinSecs 1266489956 (16:15:56)
AttributeTimeinuSecs 627000
AttributeEventSequenceNumber 00000000000002cf
16:15:56.627_T_E_ [14:0c] EventError is received for tserver SIP_TServer[SIP] - Unsupported operation
received from 65200(SIP_TServer)CTSINGVCJPAB:7010(fd=) message EventAttachedDataChanged(refid=24)


3) Default routing Now:

16:16:06.627_I_I_0fc801c76b5470d0 [09:05] >>>>>>>>>>>>resume interpretator(0)
16:16:06.627_M_I_0fc801c76b5470d0 [17:11] VQ 01d39f60 first available call: none, reason=binding
16:16:06.627_M_I_0fc801c76b5470d0 [13:03] call (virtual queue 01d354b0, id=4, priority 0) doesn't wait for VQ 01d39f60 (name="") now
request to 65200(SIP_TServer) message RequestDeletePair
AttributeReferenceID 25
AttributeDataKey 'RTargetAgentGroup'
AttributeConnID 0fc801c76b5470d0
AttributeThisDN '4000'
..sent to CTSINGVCJPAB:7010(fd=620)

16:16:06.627 Int 22000 ERROR
16:16:06.627 Int 20003 interaction 0fc801c76b5470d0 is routed to default
request to 65200(SIP_TServer) message RequestUpdateUserData


4) Finally the call is deleting

received from 65200(SIP_TServer)CTSINGVCJPAB:7010(fd=) message EventError
(Object not known)
AttributeClientID 4
AttributeThisDN '4000'
AttributeConnID 0fc801c76b5470d0
AttributeOtherDN ''
AttributeExtensions [41] 00 02 00 00..
'CUSTOMER_ID' 'Resources'
'SWITCH' 'SIP'
AttributeRouteType 1 (RouteTypeDefault)
AttributeReason [14] 00 01 01 00..
'RTR' 108
AttributeReferenceID 28
AttributeErrorMessage 'Object not known'
AttributeErrorCode 1143
AttributeTimeinSecs 1266489967 (16:16:07)
AttributeTimeinuSecs 877000
AttributeEventSequenceNumber 00000000000003a6
16:16:07.877_T_E_ [14:0c] EventError is received for tserver SIP_TServer[SIP] - Object not known
16:16:07.877_A_E_0fc801c76b5470d0 [14:32] <-----------ERROR
    _T_W_0fc801c76b5470d0 [0E:0f] emergency: delete call due to this error
16:16:07.877_I_I_0fc801c76b5470d0 [01:08] call deleting truly

Hope i could find some help on the same :-)

Cheers,

Tejal

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: SIP Server- Call Not routing
« Reply #1 on: February 23, 2010, 11:56:21 AM »
Hi Tejal,

I don't see any notes in your description about SIP softphone used by the agents 2000 and 2001. Genesys StarterApp is CTI softphone application only so the agents must use SIP softphone application (e.g. X-Lite) as well to be able to receive SIP call.

R.

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
Re: SIP Server- Call Not routing
« Reply #2 on: February 23, 2010, 02:47:49 PM »
René is right, but in addition to that, from your notes we can see only the 'Events' and not the correspondent 'Requests' that generated them, please upload the whole log next time ;)

Cheers,

Fra