" /> Issue in Nailed-Up Agent call routing - Genesys CTI User Forum

Author Topic: Issue in Nailed-Up Agent call routing  (Read 9844 times)

Offline GenesysEng

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Issue in Nailed-Up Agent call routing
« on: November 20, 2013, 08:53:26 AM »
Advertisement
Hello,

Am facing problem in nailed-up agent call routing. As per Sip deployment guide 8.1, i have configured Nailed-up Dn with following parameter.

contact = sip:xxxxxxxxxxxxx@MediaGatewayIp:5060
dual-dialog-enabled = false
line-type = 1
refer-enabled = false
reject-call-notready = true

Below is detailed issue scenario:
1) Outbound call landed on Agent1 who is part of Site1
2) Agent1 wants to consult with other agent. So he dials routepoint.
3) From Routepoint, the call landed on Agent2 who is part of external site.
4) Agent2 is nailed-up agent & my extension number is mapped to Agent2
5) The problem is, call landed on Agent2 desktop, but the call not landed on my extension.
6) When i try to answer the call in IWS, i got "Unsupported operation(media error 51)" error message.

FYI, we are using CISCO gateway. TServer version 8.1.000.79

I have checked SipServer deployment document. But i couldn't find more information.
Even in solution search also, no information's are available. I saw a relevant post in this forum. But unfortunately the solution was not there. As first level troubleshooting, i have removed connection on both tservers & added again. And even i rebooted both tservers. But no luck.

Anyone please help..!

[b]Log snap shot from External Site:[/b]

@09:18:49.4963 [ISCC] Send to server SIPServer_OCS_rn_P@Switch_OCS_rn/1: message ISCCRequestAuthorize
ISCCAttributeTrackingID 29405608 [01c0b1a8]
ISCCAttributeReferenceID 29415596 [01c0d8ac]
ISCCAttributeTSCPVersion '8.1.001.43'
ISCCAttributeServerVersion '8.1.000.79'
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))'
ISCCAttributeServerCapabilityMask {bstring}
ISCCAttributeProtocolVersion 'ISCC protocol 5.1'
ISCCAttributeDeviceType -1 [ffffffff]
ISCCAttributeServerRole Primary
ISCCAttributeServerLocation ‘Switch_sf1’
ISCCAttributeServerName ‘SIPServer_sf1_P’
@09:18:49.4964 [ISCC] [connection b7e19e48] Sent to connection [32]2
@09:18:49.4967 [ISCC] [connection b7e19e48] Socket disconnected on connection [32]2
@09:18:49.4968 [ISCC] {server SIPServer_OCS_rn_P@Switch_OCS_rn {role backup} {disconnected}}
@09:18:49.4968 [ISCC] {server SIPServer_OCS_rn_P@Switch_OCS_rn {role backup} {connecting}}
@09:18:49.4968 [ISCC] [connection b7e19e48] connecting [0]1
09:18:49.899 Trc 04541 RequestAnswerCall received from [30] (0000d0af IWS_sf1_sf1_xxxx 206.122.161.27:49689)
message RequestAnswerCall
AttributeReferenceID 12
AttributeThisDN '00998095600823'
AttributeConnID 007802383f3aa03c
09:18:49.899 Int 04543 Interaction message "RequestAnswerCall" received from 30 ("IWS_sf1_sf1_xxxx")
09:18:49.899  -- created: CRequest@c255bb8 RequestAnswerCall-IWS_sf1_sf1_xxxx[30]/12
09:18:49.899: $+TLIB:CTI:Unknown:0:0
09:18:49.899 +++ CIFace::Request +++
  -- new invoke
  -- thisCall by party
  Parsed: RequestAnswerCall
  From: IWS_sf1_sf1_xxxx[30]/12
  Numbers: +<00998095600823> -<none>
  Calls: aea1b70:1 none
  Parties: 00998095600823.c25b0c0-aea1b70:1
          none
  Status: parsed:1 queued:0 sent:0 acked:0 preevent:0 event:0 context:0 transferred:0
  -----
  -- validate
  -- state check: ok
  CIFace: Sent CRequest@c255bb8 RequestAnswerCall-IWS_sf1_sf1_xxxx[30]/12
  -- NATimer suspended
  TNAEmulator::NotifyBackup()
  -- NAData ClRq added
  FinishRequest CRequest@c255bb8 RequestAnswerCall-IWS_sf1_sf1_xxxx[30]/12
  IFace stats: q=0 s=0
  -- complete
  -- NAData ClRq removed
  -- NATimer resumed
  TNAEmulator::NotifyBackup()
09:18:49.899: device[00998095600823]:ANSWER: No method
  Response (51): for CRequest@c255bb8 RequestAnswerCall-IWS_sf1_sf1_xxxx[30]/12
  -- thisCall by party
[b]09:18:49.899 Trc 36002 Request rejected: error code 51(Unsupported operation)[/b]
@09:18:49.8998 [0] 8.1.000.79 send_to_client: message EventError
(Unsupported operation)
AttributeEventSequenceNumber 0000000000000b81
AttributeTimeinuSecs 899863
AttributeTimeinSecs 1384935529 (09:18:49)
AttributeErrorCode 51
AttributeErrorMessage 'Unsupported operation'
AttributeConnID 007802383f3aa03c
AttributeThisDN '00998095600823'
AttributeReferenceID 12
AttributeClientID 53423
09:18:49.899 Int 04545 Interaction message "EventError" sent to 30 ("IWS_sf1_sf1_xxxx")
09:18:49.899 Trc 04542 EventError sent to [30] (0000d0af IWS_sf1_sf1_xxxx 206.122.161.27:49689)
  FinishRequest: second time for CRequest@c255bb8 RequestAnswerCall-IWS_sf1_sf1_xxxx[30]/12
09:18:49.899 --- CIFace::Request ---
09:18:49.899  -- deleted: CRequest@c255bb8 RequestAnswerCall-IWS_sf1_sf1_xxxx[30]/12
09:18:49.899: $-TLIB:CTI:Unknown:0:0

09:18:50.517 Trc 04521 New client 32 connected from '206.122.160.76'
09:18:50.517 (connection (accepted) (socket 32) (remote-host 206.122.160.76) (remote-port 9395) (listener (port-id default) (socket 9)))
@09:18:50.5172 [ISCC] [connection c248468] Connection [32]2 is created


Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Issue in Nailed-Up Agent call routing
« Reply #1 on: November 20, 2013, 09:34:04 AM »
Try to add option/parameter
[code]
sip-cti-control= talk,hold
[/code]
to the annex of the extensions

Offline GenesysEng

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Issue in Nailed-Up Agent call routing
« Reply #2 on: November 20, 2013, 10:19:23 AM »
Sure, i will try it.

But as per sip deployment document( page number 251), For nailed up agent, the option "sip-cti-control" is not require.

Please advise.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Issue in Nailed-Up Agent call routing
« Reply #3 on: November 20, 2013, 11:30:08 AM »
I know that doc says it, but try to configure it. I think it helps you.

Offline GenesysEng

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Issue in Nailed-Up Agent call routing
« Reply #4 on: November 20, 2013, 11:58:02 AM »
I tried it. But still the call not landed on my extension. In IWS, if i click "Answer" button, i got the  below error message after 30sec.

"Call has disconnected - Media Error (237)"

[b]Error msg in SipServer log:[/b]

12:49:41.047 Trc 36002 Request rejected: error code 237(call disconnected)

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Issue in Nailed-Up Agent call routing
« Reply #5 on: November 20, 2013, 01:28:57 PM »
Is still the error in SIP log same as in first occurrence or some change in this? Post whole log, please.

Offline GenesysEng

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Issue in Nailed-Up Agent call routing
« Reply #6 on: November 20, 2013, 02:57:13 PM »
Hi,

The problem is still there(Still the call not landed on my phone number. Its landed on IWS window only.)

As suggested, i added "sip-cti-control" option. When i click the "Answer" button in IWS, the call was not answered. After few sec, I got "Call has disconnected - Media Error (237" error message in IWS

Please download the logs from below URL (I send the username & password to your mail)

http://www.4shared.com/zip/8OIphaBe/3_online.html

Connid to refer : 007802383f3aa051

Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Re: Issue in Nailed-Up Agent call routing
« Reply #7 on: November 20, 2013, 07:43:05 PM »
cti-control will work only after call is already established (nailed-up) - for the first time call needs to answered manually. Problem needs to be in SIP signalling to the gateway

BTW - can You use service for sharing files that doesn't require other people to log in/register/pay to download Your files
« Last Edit: November 20, 2013, 07:47:09 PM by bublepaw »

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Issue in Nailed-Up Agent call routing
« Reply #8 on: November 21, 2013, 08:17:09 AM »
I am little bit confused from the logs, but what I see is that the SIP error message - [code]405 Method Not Allowed[/code] is occurring still before answer call request, next thing is that ISCC communication looks wrong:
[code]
@12:49:28.5381 [ISCC] Error: Missing or invalid attribute: ServerName
@12:49:28.5381 [ISCC] Server is rejected: message ISCCEventAuthorizeResponse
ISCCAttributeTrackingID 29415728 [01c0d930]
ISCCAttributeReferenceID 15437556 [00eb8ef4]
ISCCAttributeResponseCode Not_Configured
[/code]
next SIP error is [code]481 Subscription does not exist[/code]. So, as Bublepaw mentioned and I agree with him, it looks like SIP connection is not established yet - like this [code]Timer expired on connection[/code].