" /> EventDesitnationBusy for a IVR port in a GVP integration throught IVR Server. - Genesys CTI User Forum

Author Topic: EventDesitnationBusy for a IVR port in a GVP integration throught IVR Server.  (Read 11617 times)

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
Advertisement
It's a GVP integration mode throught IVR Server.

a IVR port can got eventringing, but after that, hang up, there is an EventDesitnationBusy error.

there are a lot of error msg "Unable to resolve number for DN:GVP"," Gateway for address '10.36.141.193', number 'GVP' is not found." in sip log.

Is this GVP DN a default DN? do I have to create it? does it have anything to do with the error "EventDesitnationBusy " ???

below is the related SIP log.

any thoughts?

thanks in advance.


11:08:57.852: $+NET:SIP::0:0
11:08:57.853: SIPTR: Received [0,UDP] 408 bytes from 10.36.141.193:5064 <<<<<
OPTIONS sip:10.36.141.192:5060 SIP/2.0
Via: SIP/2.0/UDP 10.36.141.193:5064;branch=z9hG4bK0000000019A774E0325309
[size=14pt][b]From: <sip:GVP@10.36.141.193:5064>;tag=21E60A5E-6099-4A94-D9A3-08BE55CA5CE4[/b][/size]
To: sip:10.36.141.192:5060
Max-Forwards: 70
CSeq: 510323 OPTIONS
Call-ID: 529C016A-4EF6-4846-C7A9-44741B8A0756-5064@10.36.141.193
Contact: <sip:GVP@10.36.141.193:5064>
Content-Length: 0
Supported: timer, uui

11:08:57.853: Unable to resolve number for DN:GVP
11:08:57.853: Unable to resolve number for DN:GVP
11:08:57.853: trunk ip addr 10.36.141.193
11:08:57.853 Std 52002 Gateway for address '10.36.141.193', number 'GVP' is not found.
11:08:57.853: Sending  [0,UDP] 327 bytes to 10.36.141.193:5064 >>>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.36.141.193:5064;branch=z9hG4bK0000000019A774E0325309;received=10.36.141.193
From: <sip:GVP@10.36.141.193:5064>;tag=21E60A5E-6099-4A94-D9A3-08BE55CA5CE4
To: sip:10.36.141.192:5060
CSeq: 510323 OPTIONS
Call-ID: 529C016A-4EF6-4846-C7A9-44741B8A0756-5064@10.36.141.193
Content-Length: 0

11:08:57.853: $-NET:SIP::0:511

11:08:58.846: $+NET:SIP::0:0
11:08:58.846: SIPTR: Received [0,UDP] 408 bytes from 10.36.141.193:5064 <<<<<
OPTIONS sip:10.36.141.192:5060 SIP/2.0
Via: SIP/2.0/UDP 10.36.141.193:5064;branch=z9hG4bK000000001A0F01E032530a
From: <sip:GVP@10.36.141.193:5064>;tag=D1970905-B329-4A08-4C83-838855EA3C4A
To: sip:10.36.141.192:5060
Max-Forwards: 70
CSeq: 510328 OPTIONS
Call-ID: 5C8D049F-03CA-49ED-6099-6D21C24A03A7-5064@10.36.141.193
Contact: <sip:GVP@10.36.141.193:5064>
Content-Length: 0
Supported: timer, uui

11:08:58.846: Unable to resolve number for DN:GVP
11:08:58.846: Unable to resolve number for DN:GVP
11:08:58.846: trunk ip addr 10.36.141.193
11:08:58.846 Std 52002 Gateway for address '10.36.141.193', number 'GVP' is not found.
11:08:58.846: Sending  [0,UDP] 327 bytes to 10.36.141.193:5064 >>>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.36.141.193:5064;branch=z9hG4bK000000001A0F01E032530a;received=10.36.141.193
From: <sip:GVP@10.36.141.193:5064>;tag=D1970905-B329-4A08-4C83-838855EA3C4A
To: sip:10.36.141.192:5060
CSeq: 510328 OPTIONS
Call-ID: 5C8D049F-03CA-49ED-6099-6D21C24A03A7-5064@10.36.141.193
Content-Length: 0

11:08:58.846: $-NET:SIP::0:459

11:08:59.853: $+NET:SIP::0:0
11:08:59.853: SIPTR: Received [0,UDP] 408 bytes from 10.36.141.193:5064 <<<<<
OPTIONS sip:10.36.141.192:5060 SIP/2.0
Via: SIP/2.0/UDP 10.36.141.193:5064;branch=z9hG4bK000000001A0EF9A032530b
From: <sip:GVP@10.36.141.193:5064>;tag=A9445E71-5094-430E-8EAF-AE93A02A349D
To: sip:10.36.141.192:5060
Max-Forwards: 70
CSeq: 510333 OPTIONS
Call-ID: 5EFED0A2-D90A-4B67-68AD-65C04E3B6289-5064@10.36.141.193
Contact: <sip:GVP@10.36.141.193:5064>
Content-Length: 0
Supported: timer, uui

[b][size=12pt][color=red]11:08:59.853: Unable to resolve number for DN:GVP
11:08:59.853: Unable to resolve number for DN:GVP[/color][/size][/b]
11:08:59.853: trunk ip addr 10.36.141.193
[color=red][b]11:08:59.853 Std 52002 Gateway for address '10.36.141.193', number 'GVP' is not found.[/b][/color]
11:08:59.853: Sending  [0,UDP] 327 bytes to 10.36.141.193:5064 >>>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.36.141.193:5064;branch=z9hG4bK000000001A0EF9A032530b;received=10.36.141.193
From: <sip:GVP@10.36.141.193:5064>;tag=A9445E71-5094-430E-8EAF-AE93A02A349D
To: sip:10.36.141.192:5060
CSeq: 510333 OPTIONS
Call-ID: 5EFED0A2-D90A-4B67-68AD-65C04E3B6289-5064@10.36.141.193
Content-Length: 0

11:08:59.853: $-NET:SIP::0:469

11:09:00.732: $+NET:SIP::0:0
11:09:00.732: SIPTR: Received [0,UDP] 882 bytes from 10.36.141.193:5060 <<<<<
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 10.36.141.192:5060;branch=z9hG4bKFC41DA6E-D364-4C67-A458-FB5285D1C7A6-33
From: sip:4001@10.36.141.192:5060;tag=7D2A1C3D-D914-4610-B03A-F02556A1F858-26
To: <sip:12001@10.36.141.192:5060>;tag=456458A8-A689-4536-2DB5-A2EA038547BE
CSeq: 1 INVITE
Call-ID: 248C1375-1D32-4C37-9F7A-0E8A45D1C9F5-14@10.36.141.192
Contact: sip:CTIConnector@10.36.141.193:5080
Content-Length: 0
Record-Route: <sip:000000000D54F1B0@10.36.141.193:5060;lr;gvp.rm.datanodes=1;idtag=00000031>
X-Genesys-GVP-Session-ID: 18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;gvp.rm.datanodes=1;gvp.rm.cti-call=1
X-Genesys-GVP-CDR: CALL-DISPOSITION=0;QUEUE-WAIT-TIME=0.000000
X-Genesys-CallInfo: routed
X-Genesys-CallUUID: E8OI3STMD150NCD4SM8SOM7A88000008
X-Genesys-GVP-Session-Data: callsession=18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;1;0;;sip:10.36.141.193:5080;;;;

11:09:00.732: Sending  [0,UDP] 451 bytes to 10.36.141.193:5060 >>>>>
ACK sip:30019@10.36.141.193:5060 SIP/2.0
Via: SIP/2.0/UDP 10.36.141.192:5060;branch=z9hG4bKFC41DA6E-D364-4C67-A458-FB5285D1C7A6-33
From: sip:4001@10.36.141.192:5060;tag=7D2A1C3D-D914-4610-B03A-F02556A1F858-26
To: <sip:12001@10.36.141.192:5060>;tag=456458A8-A689-4536-2DB5-A2EA038547BE
Call-ID: 248C1375-1D32-4C37-9F7A-0E8A45D1C9F5-14@10.36.141.192
CSeq: 1 ACK
Max-Forwards: 69
User-Agent: X-Lite release 1100l stamp 47546
Content-Length: 0

11:09:00.732: SipDialog: event CALLING_RESREJECT, t=1694, s=9, r=5, m=00000000040a0788
11:09:00.732 SIPCONN(30019): HandleSipDialogEvent(CALLING_RESREJECT)
11:09:00.732 SIPCONN(30019): 1pcc event CALLING_RESREJECT
11:09:00.732 SIPCONN(30019): ConvertResponse: 480
11:09:00.732 SIPCONN(30019): ConvertResponse: no conversion configured for 480
11:09:00.733 SIPCONN(30019): state e:4,p:2,s:6,c:10,rc:480,m:1
11:09:00.733 SIPPARTY(30019): 24 verify update of party-connection state A-F
11:09:00.733 SIPPARTY(30019): 24 update party-connection state A-F
11:09:00.733 +++ CIFace::Event +++
  +++ Pre-event +++
    Type EventDestinationBusy
    Devices: <4001/4001> <30019/30019> <-/->
    Calls: 8/00700212bebaa008/8.04016330/c:2/r:1 0/none
    Parties:    D4001/4001.03f10af0-04016330:1/l:1/r:0/Dialing,Active,Origination
                D30019/30019.035548a0-04016330:1/l:2/r:0/Alerting,DNull,Destination
                none
    Cause: Busy/3, Info: 0
    Flags: divert=0 hook=0 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=1
  --- Pre-event ---
  +++ DestBusy +++
    -- target state not compatible at line 1174
    SetFailed: party 4001.03f10af0-04016330:1, cause Busy
@11:09:00.7330 [0] 8.1.000.79 [size=12pt][b]distribute_event: message EventDestinationBusy[/b][/size]
        AttributeEventSequenceNumber    000000000000124a
        AttributeTimeinuSecs    733000
        AttributeTimeinSecs    1345475340 (11:09:00)
        AttributeExtensions    [23] 00 01 01 00..
                'BusinessCall'  0
        AttributeOtherDNRole    2
        AttributeOtherDN        '30019'
        AttributeThisDNRole    1
        AttributeThisDN '4001'
        AttributeCustomerID    'Resources'
        AttributeDNIS  '12001'
        AttributeUserData      [567] 00 17 00 00..
                'userdata1'    'test1'

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Hi Kevin,

The error message 52002 (Gateway for address...) is caused by missing Trunk DN object in Genesys configuration with IP address 10.36.141.193.

Your issue is caused by 480 Temporarily Unavailable error that is returned as response to original INVITE. I assume this error is returned by Resource Manager but it could be error from CTI Connector as well.
[quote]11:09:00.732: SIPTR: Received [0,UDP] 882 bytes from 10.36.141.193:5060 <<<<<
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 10.36.141.192:5060;branch=z9hG4bKFC41DA6E-D364-4C67-A458-FB5285D1C7A6-33
From: sip:4001@10.36.141.192:5060;tag=7D2A1C3D-D914-4610-B03A-F02556A1F858-26
To: <sip:12001@10.36.141.192:5060>;tag=456458A8-A689-4536-2DB5-A2EA038547BE
CSeq: 1 INVITE
Call-ID: 248C1375-1D32-4C37-9F7A-0E8A45D1C9F5-14@10.36.141.192
Contact: sip:CTIConnector@10.36.141.193:5080
Content-Length: 0
Record-Route: <sip:000000000D54F1B0@10.36.141.193:5060;lr;gvp.rm.datanodes=1;idtag=00000031>
X-Genesys-GVP-Session-ID: 18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;gvp.rm.datanodes=1;gvp.rm.cti-call=1
X-Genesys-GVP-CDR: CALL-DISPOSITION=0;QUEUE-WAIT-TIME=0.000000
X-Genesys-CallInfo: routed
X-Genesys-CallUUID: E8OI3STMD150NCD4SM8SOM7A88000008
X-Genesys-GVP-Session-Data: callsession=18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;1;0;;sip:10.36.141.193:5080;;;;[/quote]

R.

PS. Sorry for no-reply on your PM. I simply forgot :-(


Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
[quote author=René link=topic=7368.msg31503#msg31503 date=1345490082]
Hi Kevin,

The error message 52002 (Gateway for address...) is caused by missing Trunk DN object in Genesys configuration with IP address 10.36.141.193.

Your issue is caused by 480 Temporarily Unavailable error that is returned as response to original INVITE. I assume this error is returned by Resource Manager but it could be error from CTI Connector as well.
[quote]11:09:00.732: SIPTR: Received [0,UDP] 882 bytes from 10.36.141.193:5060 <<<<<
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 10.36.141.192:5060;branch=z9hG4bKFC41DA6E-D364-4C67-A458-FB5285D1C7A6-33
From: sip:4001@10.36.141.192:5060;tag=7D2A1C3D-D914-4610-B03A-F02556A1F858-26
To: <sip:12001@10.36.141.192:5060>;tag=456458A8-A689-4536-2DB5-A2EA038547BE
CSeq: 1 INVITE
Call-ID: 248C1375-1D32-4C37-9F7A-0E8A45D1C9F5-14@10.36.141.192
Contact: sip:CTIConnector@10.36.141.193:5080
Content-Length: 0
Record-Route: <sip:000000000D54F1B0@10.36.141.193:5060;lr;gvp.rm.datanodes=1;idtag=00000031>
X-Genesys-GVP-Session-ID: 18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;gvp.rm.datanodes=1;gvp.rm.cti-call=1
X-Genesys-GVP-CDR: CALL-DISPOSITION=0;QUEUE-WAIT-TIME=0.000000
X-Genesys-CallInfo: routed
X-Genesys-CallUUID: E8OI3STMD150NCD4SM8SOM7A88000008
X-Genesys-GVP-Session-Data: callsession=18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;1;0;;sip:10.36.141.193:5080;;;;[/quote]

R.

PS. Sorry for no-reply on your PM. I simply forgot :-(
[/quote]

Rene, Thank you very much, I need to check RM log more carefully.

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
[quote author=René link=topic=7368.msg31503#msg31503 date=1345490082]
Hi Kevin,

The error message 52002 (Gateway for address...) is caused by missing Trunk DN object in Genesys configuration with IP address 10.36.141.193.

Your issue is caused by 480 Temporarily Unavailable error that is returned as response to original INVITE. I assume this error is returned by Resource Manager but it could be error from CTI Connector as well.
[quote]11:09:00.732: SIPTR: Received [0,UDP] 882 bytes from 10.36.141.193:5060 <<<<<
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 10.36.141.192:5060;branch=z9hG4bKFC41DA6E-D364-4C67-A458-FB5285D1C7A6-33
From: sip:4001@10.36.141.192:5060;tag=7D2A1C3D-D914-4610-B03A-F02556A1F858-26
To: <sip:12001@10.36.141.192:5060>;tag=456458A8-A689-4536-2DB5-A2EA038547BE
CSeq: 1 INVITE
Call-ID: 248C1375-1D32-4C37-9F7A-0E8A45D1C9F5-14@10.36.141.192
Contact: sip:CTIConnector@10.36.141.193:5080
Content-Length: 0
Record-Route: <sip:000000000D54F1B0@10.36.141.193:5060;lr;gvp.rm.datanodes=1;idtag=00000031>
X-Genesys-GVP-Session-ID: 18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;gvp.rm.datanodes=1;gvp.rm.cti-call=1
X-Genesys-GVP-CDR: CALL-DISPOSITION=0;QUEUE-WAIT-TIME=0.000000
X-Genesys-CallInfo: routed
X-Genesys-CallUUID: E8OI3STMD150NCD4SM8SOM7A88000008
X-Genesys-GVP-Session-Data: callsession=18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;1;0;;sip:10.36.141.193:5080;;;;[/quote]

R.

PS. Sorry for no-reply on your PM. I simply forgot :-(
[/quote]

I have the all the related logs for one specific call and exported CFG DB, can you help take a quick look?

Kevin.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Try to create Voice over IP Service which is called "GVP",pointed to RM and is set like an application (service-type=application).
I have this settings in my LAB and all works fine

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
[quote author=Kubig link=topic=7368.msg31519#msg31519 date=1345559864]
Try to create Voice over IP Service which is called "GVP",pointed to RM and is set like an application (service-type=application).
I have this settings in my LAB and all works fine
[/quote]

Thanks you for  sharing your experience.

I just tried, still got EventDestinationBusy.

Kevin

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
[quote author=René link=topic=7368.msg31503#msg31503 date=1345490082]
Hi Kevin,

The error message 52002 (Gateway for address...) is caused by missing Trunk DN object in Genesys configuration with IP address 10.36.141.193.

Your issue is caused by 480 Temporarily Unavailable error that is returned as response to original INVITE. I assume this error is returned by Resource Manager but it could be error from CTI Connector as well.
[quote]11:09:00.732: SIPTR: Received [0,UDP] 882 bytes from 10.36.141.193:5060 <<<<<
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 10.36.141.192:5060;branch=z9hG4bKFC41DA6E-D364-4C67-A458-FB5285D1C7A6-33
From: sip:4001@10.36.141.192:5060;tag=7D2A1C3D-D914-4610-B03A-F02556A1F858-26
To: <sip:12001@10.36.141.192:5060>;tag=456458A8-A689-4536-2DB5-A2EA038547BE
CSeq: 1 INVITE
Call-ID: 248C1375-1D32-4C37-9F7A-0E8A45D1C9F5-14@10.36.141.192
Contact: sip:CTIConnector@10.36.141.193:5080
Content-Length: 0
Record-Route: <sip:000000000D54F1B0@10.36.141.193:5060;lr;gvp.rm.datanodes=1;idtag=00000031>
X-Genesys-GVP-Session-ID: 18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;gvp.rm.datanodes=1;gvp.rm.cti-call=1
X-Genesys-GVP-CDR: CALL-DISPOSITION=0;QUEUE-WAIT-TIME=0.000000
X-Genesys-CallInfo: routed
X-Genesys-CallUUID: E8OI3STMD150NCD4SM8SOM7A88000008
X-Genesys-GVP-Session-Data: callsession=18C214C9-FD60-4F6A-DFBF-069B3A3E52BF;1;0;;sip:10.36.141.193:5080;;;;[/quote]

R.

PS. Sorry for no-reply on your PM. I simply forgot :-(
[/quote]

forgot to tell, Cfg DB is oracle.

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
[quote author=Kubig link=topic=7368.msg31519#msg31519 date=1345559864]
Try to create Voice over IP Service which is called "GVP",pointed to RM and is set like an application (service-type=application).
I have this settings in my LAB and all works fine
[/quote]

That DN is used for a behind SIP Server implementation, this one is instead via IVR Server.

Fra

Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Hi Kevin,

As mentioned at some other threads - do You really need integration through IVR server? Integration through SIP is much easier to configure and debug.

Pawel

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
[quote author=Fra link=topic=7368.msg31529#msg31529 date=1345626586]
[quote author=Kubig link=topic=7368.msg31519#msg31519 date=1345559864]
Try to create Voice over IP Service which is called "GVP",pointed to RM and is set like an application (service-type=application).
I have this settings in my LAB and all works fine
[/quote]

That DN is used for a behind SIP Server implementation, this one is instead via IVR Server.

Fra
[/quote]

Sure, you're right. I noticed,that this is a IVR and not SIP,later.

Offline kevinwang

  • Full Member
  • ***
  • Posts: 159
  • Karma: 0
[quote author=bublepaw link=topic=7368.msg31541#msg31541 date=1345640856]
Hi Kevin,

As mentioned at some other threads - do You really need integration through IVR server? Integration through SIP is much easier to configure and debug.

Pawel
[/quote]

YOu are totally right, INtegration through sipserver is easier and more straightforward,,,easy for debug....

but I migrated from a legacy system, the integration mode of which is through IVR Server.