Invalid Calling DN | ESDK | VoiceService.MakeCall

[jesuissur]

Hi there,

We are trying to use the simple example provided by Genesys under the Tech Tutorial #60 ([url=https://genesyslab.com/support/tutorials/recorded_detail.asp?item=B8C93DA63FA831AA33AC3541BAC43746]https://genesyslab.com/support/tutorials/recorded_detail.asp?item=B8C93DA63FA831AA33AC3541BAC43746[/url]) but we get the following error message while doing the call to VoiceService.MakeCall().

[code]
2012-02-15 14:53:37,261 DEBUG Proxy got message 'EventError' ('52')
message attributes:
AttributeErrorMessage [str] = "Invalid Calling Dn"
CallHistory    = ComplexClass(CallHistoryInfo):
LastParty      = ComplexClass(LastRemoteParty):
FirstParty      = ComplexClass(FirstRemoteParty):
AttributeLocation [str] = ""
AttributeMakeCallType [int] = 0 [Regular]
AttributeEventSequenceNumber [long] = 5933
AttributeClientID [int] = 22
AttributeThisDN [str] = "6003"
Time            = ComplexClass(TimeStamp):
AttributeTimeinuSecs [int] = 478000
AttributeTimeinSecs [int] = 1329335206
AttributeOtherDN [str] = "1604"
AttributeErrorCode [int] = 61
AttributeReferenceID [int] = 9

[/code]

By now, we are able to login with a user and change our state to Ready.
But we can't receive any call neither make one.

Does anyone have an idea why we are unable to receive or make any call?
Why could we have an invalid DN while being able to logged in and change state of our user?

Thank you very much
Phil

[René]

Hi Phil,

Do you have corresponding log of T-Server showing your request and the error? Could you post it here?

R.

[jesuissur]

Hi René,

Since our first post, we've found a way to make the Tutorial works.
To do so, our agent must be logged off from InteractionWorkspace but still log on.
It means InteractionWorkspace is still open with our agent but this agent is in logged off state.
That way, the tutorial worked fine.  We can make and receive call with the custom application.
We still do not understand why though.

This is an excerpt of our SipServer log about Invalid calling DN.

Thank you very much
Phil

[code]

09:34:11.548 Int 04543 Interaction message "RequestMakeCall" received from 580 ("default")
09:34:11.548  -- created: CRequest@02dbf070 RequestMakeCall-default[580]/4
09:34:11.548: $+TLIB:CTI:Unknown:0:50060149
09:34:11.548 +++ CIFace::Request +++
  -- new invoke
  Parsed: RequestMakeCall
  From: default[580]/4
  Numbers: +<6003> +<6002>
  Status: parsed:1 queued:0 sent:0 acked:0 preevent:0 event:0 context:0 transferred:0
  -----
  -- validate
  -- state check: ok
  CIFace: Sent CRequest@02dbf070 RequestMakeCall-default[580]/4
  FinishRequest CRequest@02dbf070 RequestMakeCall-default[580]/4
  IFace stats: q=0 s=0
  -- complete
09:34:11.548: Unable to resolve number for DN:6003
09:34:11.548: SIPDM: failed to get registration info for 6003
09:34:11.548: SIPDM: failed to get registration info for 6003
09:34:11.552: COS:MakeCall: request from 6003 to 6002 is rejected by dial plan
  Response (61): for CRequest@02dbf070 RequestMakeCall-default[580]/4
09:34:11.558 Trc 36002 Request rejected: error code 61(Invalid Calling Dn)
@09:34:11.5580 [0] 8.1.000.44 send_to_client: message EventError
(Invalid Calling Dn)
AttributeEventSequenceNumber 00000000000107e0
AttributeTimeinuSecs 558000
AttributeTimeinSecs 1329834851 (09:34:11)
AttributeErrorCode 61
AttributeErrorMessage 'Invalid Calling Dn'
AttributeMakeCallType 0 (MakeCallRegular)
AttributeOtherDN '6002'
AttributeLocation ''
AttributeThisDN '6003'
AttributeReferenceID 4
AttributeClientID 15
09:34:11.558 Int 04545 Interaction message "EventError" sent to 580 ("default")
09:34:11.558 Trc 04542 EventError sent to [580] (0000000f default 999.999.999.999:999)
  FinishRequest: second time for CRequest@02dbf070 RequestMakeCall-default[580]/4
[/code]

[René]

Hi,

SIP Server throws an error 'Invalid called DN' as there is no SIP endpoint registered (see below)

[font=courier]09:34:11.548: Unable to resolve number for DN:6003
09:34:11.548: SIPDM: failed to get registration info for 6003[/font]

It works when Interaction Workspace is running because (I assume) Interaction Workspace SIP Endpoint is still registered thus DN is active.

R.

[jesuissur]

Thanks again.

Then, is anyone has an idea how we could register our SIP endpoint through the Enterprise SDK?
Does anyone has been successful at running this Tutorial in their environment?

We've compared the SIP server logs between Interaction Workspace and the app from the Tutorial and we noticed this specific part generated only when logging through InteractionWorkspace.
It might be significant to someone.

[quote]
11:15:34.307: Sending  [0,UDP] 460 bytes to 888.999.999.999:36414 >>>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 888.999.999.999:36414;branch=z9hG4bK-d8754z-3d3b3c1bb9d5c747-1---d8754z-;rport;received=888.999.999.999
To: <sip:6003@999.999.999.999:5088>;tag=8908A483-E1E7-45EE-87DF-698530BA56A8-15
From: <sip:6003@999.999.999.999:5088>;tag=746fa83b
Call-ID: MWNiZmNkNmEzNzMyZDZmNzgzNGE2MDUxNzU4MjlmN2Y.
CSeq: 1 REGISTER
Expires: 3600
Contact: <sip:6003@888.999.999.999:36414;rinstance=e76bc1afcdc3f532;transport=udp>;expires=3600
Content-Length: 0


11:15:34.307: [b]SetDnInService[/b]: DN 6003 in Service
@11:15:34.3070 [0] 8.1.000.44 distribute_event: message EventDNBackInService
AttributeEventSequenceNumber 000000000000024d
AttributeTimeinuSecs 307000
AttributeTimeinSecs 1329840934 (11:15:34)
AttributeThisDN '6003'
[/quote]

Thanks
Phil

[René]

Hi Phil,

You can't register SIP endpoint with Enterprise SDK. Simply it isn't functionality provided by Enterprise SDK.

Genesys offers SIP Endpoint SKD allowing you development of custom SIP softphone. Or you can use some of existing SIP softphone e.g. Bria from Counterpath.

R.

[jesuissur]

Thanks René.

Do you think it would be possible to achieve this by using only the Platform SDK instead of the Enterprise and SIP Endpoint SDK's?

Thanks
Phil

[René]

Hi Phil,

Simple answer - no. As I wrote, neither Platform SDK nor Enterprise SDK support SIP protocol. You must use SIP Endpoint SDK that belongs to Platform SDK family or 3rd party SIP SDK/softphone/hardphone.

Are you developing new CTI and SIP softphone?

R.