Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: _Lee on October 21, 2008, 08:25:29 PM
-
I get this message when routing to and agent target on a SIP TServer. The URS is running and there is a valid connection to URS.
Has anyone else seen something similar?
-Lee
-
Actually the fulle message is " ERROR: URS is not running and default routing destination is not configured."
-
Is the SIP Server on URS connections?
-
when it is no conneciton form URS to TServer.
I got the message.
sipcs: party [6000@00fbaab0:1] :11:27:37.734 EventRouteRequest timeout expired for call:006b01906ec19001
sipcs: ERROR: URS is not running and default routing destination is not configured.
-
Sorry?
-
I might have the same issue, this is an extract from a ticket that I have raised. See if you are getting the same messages in your log file.
[code]
Components:
* SIP Extension 7071 running sip softphone (X-Lite)
* SIP TServer route point 29666, Strategy ****. This will play announcement 99161001 then a TRoute (RouteTypeUnknown) to 70003
Call placed from extension 7071 to RSI 29666. the RP 29666 receives the EventRouteRequest. URS logs show the strategy is called and the announcement 99161001 is requested as expected. Then the following message is seen in the TServer log
sipcs: party [29666@03f7d6a8:1] :15:28:39.875 EventRouteRequest timeout expired for call:0574019d942df3cf
sipcs: ERROR: URS is not running and default routing destination is not configured.
sipcs: Start URS or configure default-dn parameter.
The caller experience from 7071 is that the call is not connected and ring out until it is released at 15:28:40.438
This behaviour starts at 15:28:33.8750 and impacts 4 calls until there is an EventRegistered at 15:29:30.7060 and the behaviour returns to what is expected for number of calls.
At 15:30:20.240 call 0574019d942df3de fails and every call until the next EventRegistered at 15:31:30.7280, after which the behaviour returns back to what is expected.
The cycle keeps going on and on.
[/code]
-
Hi,
Could you post here log of SIP Server covering the problematic call from the beginning to the time when described issue occurs?
I would say the issue is caused by delay on either URS or StreamManager side. SIP Server expects to receive an instruction from URS what to do with the call within defined timeout. If it doesn't receive any instruction then default routing takes place.
R.
-
Lee,
did it solve your problem?
By the way, are you using Net.Com VoIP GW? Because then the issue is not Genesys at all.