Basic call from sip server to avaya tserver

[janesh22]

Hi everyone,

Thanks for the help . Got it going at last .

[ryusuf]

Hi,

I am not sure whether i am posting under the right topic or i need to create a new topic.

From what i have read in this topic, the issue which i am facing seems to be similar.

I have a Geneys SIP server and Avaya Session Manager. I had created one trunk for both incoming [b]from Avaya SM to Genesys SIPS[/b] and [b]outgoing to Avaya SM from SIP server.[/b] However, my issue is that when i try to dial from Genesys Workspace to Avaya, i get an error "Invalid Called DN-Media Error(71)-voice (1000@SIP_Switch)"

The trunk has been configured with the following options where 192.168.10.144 is the IP address of the Session Manager.

[TServer]
contact = sip:192.168.10.144:5060
oos-check = 30
oos-force = 10
oosp-transfer-enabled = true
prefix = 9
refer-enabled = false
replace-prefix =


When checking the SIP logs i can find that the Trunk is going Out of Service. OOS Forced.

[b]Below is the excerpt from the SIP logs[/b]

-----------------------------------------------------------------------------
10:19:44.138: GSProxyRegistrar:ActiveTransport In Service for dn 'msml-dn' '192.168.10.193:5060:1'
10:19:44.138: $-NET:SIP::0:79

-AP[4]-<-552 @10:19:44.4350
-Ap[4]->-552 @10:19:44.4350
10:19:46.638: Sending  [0,UDP] 398 bytes to 192.168.10.144:5060 >>>>>
OPTIONS sip:JCCI_Trunk@192.168.10.144:5060 SIP/2.0
From: <sip:JCCI_Trunk@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-7
To: <sip:JCCI_Trunk@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-7@192.168.10.191
CSeq: 1456730379 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK3C0C5CD6-78F9-4148-A1ED-CF11655D61BE
Max-Forwards: 0


10:19:49.138: TRANSPCHK[JCCI_Trunk:192.168.10.144:5060]:OOS FORCED
10:19:49.138: TRANSPCHK[JCCI_Trunk:192.168.10.144:5060]:DETECTED OUT OF SERVICE
10:19:49.138: GSProxyRegistrar:ActiveTransport Out Of Service for dn 'JCCI_Trunk' '192.168.10.144:5060:1'
10:19:49.138: SetDnInService: DN JCCI_Trunk Out of Service
@10:19:49.1380 [0] 8.1.101.91 distribute_event: message EventDNOutOfService
AttributeEventSequenceNumber 00000000000001b8
AttributeTimeinuSecs 138000
AttributeTimeinSecs 1456730389 (10:19:49)
AttributeThisDN 'JCCI_Trunk'
2016-02-29T10:19:49.138 Trc 04542 EventDNOutOfService sent to [636] (00000004 ICON 192.168.10.191:62582)
2016-02-29T10:19:49.138 Trc 04542 EventDNOutOfService sent to [660] (00000005 ORS 192.168.10.191:62583)
10:19:49.138: GSDNChecker: JCCI_Trunk OutOfService due to a communication failure (ACTIVE CHECK)
2016-02-29T10:19:49.138 Std 52000 Device 'JCCI_Trunk' is out of service.
10:19:49.138: GSDNChecker:[JCCI_Trunk]:DETECTED OUT OF SERVICE
10:19:49.138: Sending  [0,UDP] 391 bytes to 192.168.10.193:5060 >>>>>
OPTIONS sip:msml-dn@192.168.10.193:5060 SIP/2.0
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-10
To: <sip:msml-dn@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-10@192.168.10.191
CSeq: 1456730389 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK55937962-C139-4D42-9695-8D34C9C251D7
Max-Forwards: 0


10:19:49.138: $+NET:SIP::0:0
10:19:49.138: SIPTR: Received [0,UDP] 382 bytes from 192.168.10.193:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK55937962-C139-4D42-9695-8D34C9C251D7
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-10
To: <sip:msml-dn@192.168.10.191:5060>;tag=5A54F106-4338-45AE-70B2-1ABE8E1175CB
CSeq: 1456730389 OPTIONS
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-10@192.168.10.191
Content-Length: 0


10:19:49.138: GSProxyRegistrar:ActiveTransport In Service for dn 'msml-dn' '192.168.10.193:5060:1'
10:19:49.138: $-NET:SIP::0:83

-AP[5]-<-664 @10:19:49.4350
-Ap[5]->-664 @10:19:49.4350
-AP[5]-<-668 @10:19:49.6380
-Ap[5]->-668 @10:19:49.6380
-AP[5]-<-672 @10:19:50.4660
-Ap[5]->-672 @10:19:50.4660
-AP[6]->-484 @10:19:51.0130
-Ap[6]-<-484 @10:19:51.0130
-AP[5]-<-552 @10:19:51.4510
-Ap[5]->-552 @10:19:51.4510
10:19:54.138: Sending  [0,UDP] 391 bytes to 192.168.10.193:5060 >>>>>
OPTIONS sip:msml-dn@192.168.10.193:5060 SIP/2.0
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-11
To: <sip:msml-dn@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-11@192.168.10.191
CSeq: 1456730394 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bKF92A3D40-7489-40F5-8F1A-5B7F45A89865
Max-Forwards: 0


10:19:54.138: $+NET:SIP::0:0
10:19:54.138: SIPTR: Received [0,UDP] 382 bytes from 192.168.10.193:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bKF92A3D40-7489-40F5-8F1A-5B7F45A89865
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-11
To: <sip:msml-dn@192.168.10.191:5060>;tag=9939FCC3-8A57-4F54-B29C-31A69516BFDD
CSeq: 1456730394 OPTIONS
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-11@192.168.10.191
Content-Length: 0


10:19:54.138: GSProxyRegistrar:ActiveTransport In Service for dn 'msml-dn' '192.168.10.193:5060:1'
10:19:54.138: $-NET:SIP::0:81

-AP[1]->-636 @10:19:54.4040
-AP[1]->-660 @10:19:54.4040
-Ap[1]-<-636 @10:19:54.4040
-Ap[1]-<-660 @10:19:54.4040
-AP[6]-<-664 @10:19:56.4350
-Ap[6]->-664 @10:19:56.4350
-AP[6]-<-668 @10:19:56.6540
-Ap[6]->-668 @10:19:56.6540
-AP[6]-<-672 @10:19:57.4660
-Ap[6]->-672 @10:19:57.4660
-AP[7]->-484 @10:19:58.0130
-Ap[7]-<-484 @10:19:58.0130
-AP[6]-<-552 @10:19:58.4660
-Ap[6]->-552 @10:19:58.4660
10:19:59.138: Sending  [0,UDP] 391 bytes to 192.168.10.193:5060 >>>>>
OPTIONS sip:msml-dn@192.168.10.193:5060 SIP/2.0
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-12
To: <sip:msml-dn@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-12@192.168.10.191
CSeq: 1456730399 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK118F9DB3-90DF-4E12-8D15-CF8DCF931BFA
Max-Forwards: 0


10:19:59.138: $+NET:SIP::0:0
10:19:59.138: SIPTR: Received [0,UDP] 382 bytes from 192.168.10.193:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK118F9DB3-90DF-4E12-8D15-CF8DCF931BFA
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-12
To: <sip:msml-dn@192.168.10.191:5060>;tag=A303F26C-CACF-4FB4-C8AB-51C8CDCC3D06
CSeq: 1456730399 OPTIONS
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-12@192.168.10.191
Content-Length: 0


10:19:59.138: GSProxyRegistrar:ActiveTransport In Service for dn 'msml-dn' '192.168.10.193:5060:1'
10:19:59.138: $-NET:SIP::0:86

-AP[5]-<-660 @10:20:01.4040
-Ap[5]->-660 @10:20:01.4040
-AP[5]-<-636 @10:20:01.4040
-Ap[5]->-636 @10:20:01.4040
-AP[7]-<-664 @10:20:03.4350
-Ap[7]->-664 @10:20:03.4350
-AP[7]-<-668 @10:20:03.6700
-Ap[7]->-668 @10:20:03.6700
10:20:04.138: Sending  [0,UDP] 391 bytes to 192.168.10.193:5060 >>>>>
OPTIONS sip:msml-dn@192.168.10.193:5060 SIP/2.0
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-13
To: <sip:msml-dn@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-13@192.168.10.191
CSeq: 1456730404 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bKFE2ADAB1-26C5-4AD5-8A31-00201D17CF77
Max-Forwards: 0


10:20:04.138: $+NET:SIP::0:0
10:20:04.138: SIPTR: Received [0,UDP] 382 bytes from 192.168.10.193:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bKFE2ADAB1-26C5-4AD5-8A31-00201D17CF77
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-13
To: <sip:msml-dn@192.168.10.191:5060>;tag=A0AF611F-0B3F-4B1D-B2BC-487C1C7806FE
CSeq: 1456730404 OPTIONS
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-13@192.168.10.191
Content-Length: 0


10:20:04.138: GSProxyRegistrar:ActiveTransport In Service for dn 'msml-dn' '192.168.10.193:5060:1'
10:20:04.138: $-NET:SIP::0:78

-AP[7]-<-672 @10:20:04.4670
-Ap[7]->-672 @10:20:04.4670
-AP[8]->-484 @10:20:05.0130
-Ap[8]-<-484 @10:20:05.0130
-AP[7]-<-552 @10:20:05.4980
-Ap[7]->-552 @10:20:05.4980
-AP[6]-<-660 @10:20:08.4040
-Ap[6]->-660 @10:20:08.4040
-AP[6]-<-636 @10:20:08.4040
-Ap[6]->-636 @10:20:08.4040
GLM_CO(tserver_sdn:switch_101,0,2)=4
10:20:09.138: Sending  [0,UDP] 391 bytes to 192.168.10.193:5060 >>>>>
OPTIONS sip:msml-dn@192.168.10.193:5060 SIP/2.0
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-14
To: <sip:msml-dn@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-14@192.168.10.191
CSeq: 1456730409 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bKF9BD3E73-52B5-4FD1-A5BE-6F0B2D6B99DE
Max-Forwards: 0


10:20:09.138: $+NET:SIP::0:0
10:20:09.138: SIPTR: Received [0,UDP] 382 bytes from 192.168.10.193:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bKF9BD3E73-52B5-4FD1-A5BE-6F0B2D6B99DE
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-14
To: <sip:msml-dn@192.168.10.191:5060>;tag=4AFB6A69-6157-45EB-6EA9-4A110CDB85EB
CSeq: 1456730409 OPTIONS
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-14@192.168.10.191
Content-Length: 0


10:20:09.138: GSProxyRegistrar:ActiveTransport In Service for dn 'msml-dn' '192.168.10.193:5060:1'
10:20:09.138: $-NET:SIP::0:85

GLM_EV(op=1,res=0,ud=1)
2016-02-29T10:20:10.045 Std 07101 Feature 'tserver_sdn': 10 licenses checked out
LICENSE: seat=10
-AP[8]-<-664 @10:20:10.4350
-Ap[8]->-664 @10:20:10.4350
-AP[8]-<-668 @10:20:10.6850
-Ap[8]->-668 @10:20:10.6850
-AP[8]-<-672 @10:20:11.4820
-Ap[8]->-672 @10:20:11.4820
-AP[9]->-484 @10:20:12.0130
-Ap[9]-<-484 @10:20:12.0130
-AP[8]-<-552 @10:20:12.4980
-Ap[8]->-552 @10:20:12.4980
10:20:14.138: Sending  [0,UDP] 391 bytes to 192.168.10.193:5060 >>>>>
OPTIONS sip:msml-dn@192.168.10.193:5060 SIP/2.0
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-15
To: <sip:msml-dn@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-15@192.168.10.191
CSeq: 1456730414 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK71C16E56-3478-4FFD-BEFC-C5BDF1844BDC
Max-Forwards: 0


10:20:14.138: $+NET:SIP::0:0
10:20:14.138: SIPTR: Received [0,UDP] 382 bytes from 192.168.10.193:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK71C16E56-3478-4FFD-BEFC-C5BDF1844BDC
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-15
To: <sip:msml-dn@192.168.10.191:5060>;tag=E92AC570-468A-4A64-0EB6-588DFA13B152
CSeq: 1456730414 OPTIONS
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-15@192.168.10.191
Content-Length: 0


10:20:14.138: GSProxyRegistrar:ActiveTransport In Service for dn 'msml-dn' '192.168.10.193:5060:1'
10:20:14.138: $-NET:SIP::0:81

-AP[7]-<-636 @10:20:15.4040
-Ap[7]->-636 @10:20:15.4040
-AP[7]-<-660 @10:20:15.4200
-Ap[7]->-660 @10:20:15.4200
-AP[9]-<-664 @10:20:17.4350
-Ap[9]->-664 @10:20:17.4350
-AP[9]-<-668 @10:20:17.7010
-Ap[9]->-668 @10:20:17.7010
-AP[9]-<-672 @10:20:18.4820
-Ap[9]->-672 @10:20:18.4820
-AP[10]->-484 @10:20:19.0130
-Ap[10]-<-484 @10:20:19.0130
10:20:19.138: Sending  [0,UDP] 400 bytes to 192.168.10.144:5060 >>>>>
OPTIONS sip:JCCI_Trunk@192.168.10.144:5060 SIP/2.0
From: <sip:JCCI_Trunk@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-16
To: <sip:JCCI_Trunk@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-16@192.168.10.191
CSeq: 1456730419 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK94A6F91B-555F-42D4-8838-179C63F71C44
Max-Forwards: 0


10:20:19.154: Sending  [0,UDP] 391 bytes to 192.168.10.193:5060 >>>>>
OPTIONS sip:msml-dn@192.168.10.193:5060 SIP/2.0
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-17
To: <sip:msml-dn@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-17@192.168.10.191
CSeq: 1456730419 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bKFBA738E3-C850-4378-B0C4-4FACFE1040EA
Max-Forwards: 0


10:20:19.154: $+NET:SIP::0:0
10:20:19.154: SIPTR: Received [0,UDP] 382 bytes from 192.168.10.193:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bKFBA738E3-C850-4378-B0C4-4FACFE1040EA
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-17
To: <sip:msml-dn@192.168.10.191:5060>;tag=E0D47F31-AD8C-4786-20BC-0C927C19F3CB
CSeq: 1456730419 OPTIONS
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-17@192.168.10.191
Content-Length: 0


10:20:19.154: GSProxyRegistrar:ActiveTransport In Service for dn 'msml-dn' '192.168.10.193:5060:1'
10:20:19.154: $-NET:SIP::0:86

-AP[9]-<-552 @10:20:19.5140
-Ap[9]->-552 @10:20:19.5140
10:20:19.639: Sending  [0,UDP] 400 bytes to 192.168.10.144:5060 >>>>>
OPTIONS sip:JCCI_Trunk@192.168.10.144:5060 SIP/2.0
From: <sip:JCCI_Trunk@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-16
To: <sip:JCCI_Trunk@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-16@192.168.10.191
CSeq: 1456730419 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK94A6F91B-555F-42D4-8838-179C63F71C44
Max-Forwards: 0


10:20:20.639: Sending  [0,UDP] 400 bytes to 192.168.10.144:5060 >>>>>
OPTIONS sip:JCCI_Trunk@192.168.10.144:5060 SIP/2.0
From: <sip:JCCI_Trunk@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-16
To: <sip:JCCI_Trunk@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-16@192.168.10.191
CSeq: 1456730419 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK94A6F91B-555F-42D4-8838-179C63F71C44
Max-Forwards: 0


-AP[8]-<-636 @10:20:22.4040
-Ap[8]->-636 @10:20:22.4040
-AP[8]-<-660 @10:20:22.4350
-Ap[8]->-660 @10:20:22.4350
10:20:22.639: Sending  [0,UDP] 400 bytes to 192.168.10.144:5060 >>>>>
OPTIONS sip:JCCI_Trunk@192.168.10.144:5060 SIP/2.0
From: <sip:JCCI_Trunk@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-16
To: <sip:JCCI_Trunk@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-16@192.168.10.191
CSeq: 1456730419 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK94A6F91B-555F-42D4-8838-179C63F71C44
Max-Forwards: 0


10:20:24.154: Sending  [0,UDP] 391 bytes to 192.168.10.193:5060 >>>>>
OPTIONS sip:msml-dn@192.168.10.193:5060 SIP/2.0
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-18
To: <sip:msml-dn@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-18@192.168.10.191
CSeq: 1456730424 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK80AF9D51-2CB8-4608-821C-944E046BFA27
Max-Forwards: 0


10:20:24.154: $+NET:SIP::0:0
10:20:24.154: SIPTR: Received [0,UDP] 382 bytes from 192.168.10.193:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK80AF9D51-2CB8-4608-821C-944E046BFA27
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-18
To: <sip:msml-dn@192.168.10.191:5060>;tag=0DD04A20-3CAE-4352-2F9D-6F2F1DFB44C9
CSeq: 1456730424 OPTIONS
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-18@192.168.10.191
Content-Length: 0
-----------------------------------------------------------------------------------

[b]When try to make a call to an extension 7050 with prefix 9[/b]

2016-02-29T10:28:30.339 Trc 04541 RequestMakeCall received from [676] (00000009 Workspace_Agent1 192.168.10.192:55529)
message RequestMakeCall
AttributeReferenceID 6
AttributeThisDN '1000'
AttributeUserData [106] 00 02 00 00..
'IW_CaseUid' '58b2871f-c9fb-4e7f-bf43-1715d5f75681'
'IW_BundleUid' 'f64984eb-8b0c-4d2d-9334-c1f68945e76e'
AttributeLocation ''
AttributeOtherDN '97050'
AttributeMakeCallType 0 (MakeCallRegular)
2016-02-29T10:28:30.339 Int 04543 Interaction message "RequestMakeCall" received from 676 ("Workspace_Agent1")
@10:28:30.3390 [ISCC] destination_location substituted by local
@10:28:30.3390 [ISCC] destination_location substituted by local
2016-02-29T10:28:30.339  -- created: CRequest@31b6b60 RequestMakeCall-Workspace_Agent1[676]/6
10:28:30.339: $+TLIB:CTI:Unknown:0:31859173
2016-02-29T10:28:30.339 +++ CIFace::Request +++
  -- new invoke
  Parsed: RequestMakeCall
  From: Workspace_Agent1[676]/6
  Numbers: +<1000> -<97050>
  Status: parsed:1 queued:0 sent:0 acked:0 preevent:0 event:0 context:0 transferred:0
  -----
  -- validate
  -- state check: ok
  CIFace: Sent CRequest@31b6b60 RequestMakeCall-Workspace_Agent1[676]/6
  FinishRequest CRequest@31b6b60 RequestMakeCall-Workspace_Agent1[676]/6
  IFace stats: q=0 s=0
  -- complete
10:28:30.339: ResolveCallInfo: set flag DIAL_PLAN_PROCESSING
10:28:30.339: SIPTR(0): Begin step 0 - SipTransactionResolveCallInfoByDialPlan(1)
10:28:30.339: DialPlan: No dialplan defined for 1000.
10:28:30.339: GetRegistration::Unable to resolve number for DN:97050
10:28:30.339: DialPlan: No rule applied, using original destination '97050'.
10:28:30.339: DialPlan: clear flag DIAL_PLAN_PROCESSING
10:28:30.339: Number:[97050] is not internal, looking for service
10:28:30.339: GetTheBestNode:: server list for 97050 exists, but has no validated entries
10:28:30.339: Number:97050 prefix:9 gateway list not empty, but none can be selected now
10:28:30.339: Unable to resolve number for DN:97050
10:28:30.339: SIPDM: failed to get registration info for 97050
10:28:30.339: SIPDM: failed to get registration info for 97050
10:28:30.339: Call connect failed with error WRONG_NUMBER, no DialPlan script condition - rejecting call.
10:28:30.339: ERROR: 10000029, DialPlanHandleConnect(scenario, trData,result,*instruction), SipCallManagerDialPlan.cpp,2376
10:28:30.339: SIPTR(1): failed
10:28:30.339: SIPTR(0): Step 0 - SipTransactionResolveCallInfoByDialPlan(1) failed
10:28:30.339: SIPTR(0): failed
10:28:30.339: SIPCM: transaction SipScenario failed
10:28:30.339: CALLSTATE: empty, delete the call 16777217
10:28:30.339: SipCallManager::OnTransactionFailure: Internal context, doesn't notify10:28:30.339: OnRequestFailed
2016-02-29T10:28:30.339 Trc 36002 Request rejected: error code 71(Invalid Called Dn)
@10:28:30.3390 [0] 8.1.101.91 send_to_client: message EventError
(Invalid Called Dn)
AttributeEventSequenceNumber 00000000000001c5
AttributeTimeinuSecs 339000
AttributeTimeinSecs 1456730910 (10:28:30)
AttributeErrorCode 71
AttributeErrorMessage 'Invalid Called Dn'
AttributeMakeCallType 0 (MakeCallRegular)
AttributeOtherDN '97050'
AttributeLocation ''
AttributeUserData [106] 00 02 00 00..
'IW_CaseUid' '58b2871f-c9fb-4e7f-bf43-1715d5f75681'
'IW_BundleUid' 'f64984eb-8b0c-4d2d-9334-c1f68945e76e'
AttributeThisDN '1000'
AttributeReferenceID 6
AttributeClientID 9
2016-02-29T10:28:30.339 Int 04545 Interaction message "EventError" sent to 676 ("Workspace_Agent1")
2016-02-29T10:28:30.339 Trc 04542 EventError sent to [676] (00000009 Workspace_Agent1 192.168.10.192:55529)
10:28:30.339: call1 16777217 idle
2016-02-29T10:28:30.339 --- CIFace::Request ---
2016-02-29T10:28:30.339  -- deleted: CRequest@31b6b60 RequestMakeCall-Workspace_Agent1[676]/6
10:28:30.339: $-TLIB:CTI:Unknown:0:2409

10:28:34.277: Sending  [0,UDP] 393 bytes to 192.168.10.193:5060 >>>>>
OPTIONS sip:msml-dn@192.168.10.193:5060 SIP/2.0
From: <sip:msml-dn@192.168.10.191:5060>;tag=B617F1C8-22E3-484B-A8F7-B6384DB9F0DF-130
To: <sip:msml-dn@192.168.10.191:5060>
Call-ID: 4AE3A5FC-D235-45DE-A305-1B891E4A770B-128@192.168.10.191
CSeq: 1456730914 OPTIONS
Content-Length: 0
Via: SIP/2.0/UDP 192.168.10.191:5060;branch=z9hG4bK8931E6A1-266B-4534-85AD-6777DCA66115
Max-Forwards: 0


Appreciate if anyone can help me out on what am i missing.

Thank You
Best Regards

[Fra]

You seem to have incorrectly configured your dial plan, see here:

***
10:28:30.339: Number:97050 prefix:9 gateway list not empty, but none can be selected now
10:28:30.339: Unable to resolve number for DN:97050
10:28:30.339: SIPDM: failed to get registration info for 97050
10:28:30.339: SIPDM: failed to get registration info for 97050
10:28:30.339: Call connect failed with error WRONG_NUMBER, no DialPlan script condition - rejecting call.
***

Fra

[ryusuf]

Hi Fra,

Thanks for the response.

I haven't created a dial plan at the Genesys end for routing the call from Genesys->Avaya SM->Avaya CM. But there is a dial plan in SM to route it to the CM extension.

I have configured a trunk in Genesys and i am expecting Genesys to use this trunk when dialed from Workspace using this prefix 9.

From the wireshark traces running on SIP server, i can see that SIP OPTION messages are sent to the Avaya Session Manager. However, the SM did not receive it. And after the OOS timeout for not receiving the SIP 200 OK, it forces the trunk to go OUT OF SERVICE. I believe this is why, the call is not going out from the trunk.

Correct me if i am wrong.

Thank You
Best Regards

[cavagnaro]

I saw that too. Check your network, maybe a firewall is blocking some traffic.
Check on Avaya sip logs if it receives the Info messages.

[Kubig]

You have to fixed that:
[quote]From the wireshark traces running on SIP server, i can see that SIP OPTION messages are sent to the Avaya Session Manager. However, the SM did not receive it. And after the OOS timeout for not receiving the SIP 200 OK, it forces the trunk to go OUT OF SERVICE. I believe this is why, the call is not going out from the trunk.[/quote]

[ryusuf]

Hi Kubig/Cavagnaro,

Thanks for the response

As per the client, there is no firewall between the Genesys SIPS and Avaya SM.

This option messages are not reaching at all to the Avaya SM from the Genesys SIPS. However, the OPTION messages from Avaya SM is reaching Genesys SIPS and responding back with 200 OK.

Since the customer is sticking that there is no firewall between the two. The questions which are running over the head is

1) Why is the OPTION messages not reaching Avaya SM? But from SM to Genesys SIPS it reaches.
2) If i remove the [b]oos-check[/b] and [b]oos-force[/b] from the Trunk configuration options. Then SIPS sends the INVITE message, but even the INVITE message is not reaching Avaya SM.

What can be the other reasons why the OPTION messages or the INVITE messages are not reaching the Avaya SM?

Thank You
Best Regards

[Kubig]

[list type=decimal]
[li]Network[/li]
[li]Firewall[/li]
[li]Operating System[/li]
[/list]

[ryusuf]

Hi Kubig,

For sure, its not Genesys end?

Anything to do with [b]Request-URI, or SIP headers etc[/b].. I am least knowledgeable on SIP related things. Spare me if am asking something lame.

For Genesys to connect to Avaya CM using Avaya Session Manager, we just have to create a Trunk DN at the Genesys end with the options which i have mentioned? And a dial plan at the Avaya SM right?

Thank You
Best Regards
Rashid

[Kubig]

Did you configure the "request-uri" on trunk DN related to the AvayaSM? If yes, what is the current configuration and why this options was configured?

[cavagnaro]

See SIP logs, to where are these packets being sent? Something must be wrong on your configuration or network.
Conf: bad ip, bad port
Net: something blocking traffic. as per ISO layers you know that software doesn't handle transport, what does it? Yeah...physical layer, meaning? LAN. So check your LAN. Only way software can affect if by a firewall or a bad network configuration like a bad gateway.
Can you telnet Avaya SIP port from Genesys server?

[hsujdik]

Does the host where the sip server resides has a route to the avaya sm subnet, on the signaling network card?

[ryusuf]

[quote author=Kubig link=topic=9043.msg42439#msg42439 date=1456751784]
Did you configure the "request-uri" on trunk DN related to the AvayaSM? If yes, what is the current configuration and why this options was configured?
[/quote]

Hi Kubig,

No i haven't configured "request-uri" on trunk DN. The trunk DN configuration is as below

[TServer]
contact = sip:192.168.10.144:5060
oosp-transfer-enabled = true
prefix = 9
refer-enabled = false
replace-prefix =

As per the Avaya SM engineer, they use a Domain name. But how do we configure that domain name in the Genesys trunk DN?

[quote author=cavagnaro link=topic=9043.msg42441#msg42441 date=1456756432]
See SIP logs, to where are these packets being sent? Something must be wrong on your configuration or network.
Conf: bad ip, bad port
Net: something blocking traffic. as per ISO layers you know that software doesn't handle transport, what does it? Yeah...physical layer, meaning? LAN. So check your LAN. Only way software can affect if by a firewall or a bad network configuration like a bad gateway.
Can you telnet Avaya SIP port from Genesys server?

[/quote]

Hi Cavagnaro,

The SIP request is as follows INVITE sip:7050@192.168.10.144:5060.

Here 7050 is the DN in the Avaya CM which i am trying to dial from Genesys and 192.168.10.144 is the Avaya SM which is configured in the trunk as mentioned above.

Both Genesys server and the Avaya SM are on the same subnet and as per the client, there is no firewall between these. However, i shall double check and verify with the network team again.

Yes i am able to telnet Avaya SIP port 5060 from the Genesys SIP server.


[quote author=hsujdik link=topic=9043.msg42443#msg42443 date=1456762260]
Does the host where the sip server resides has a route to the avaya sm subnet, on the signaling network card?
[/quote]

Hi,

Yes both of them are on the same subnet.

Thank You
Best Regards

[cavagnaro]

Wait, number is 7050 and prefix is 9? Create another trunk with prefix 7

[ryusuf]

Hi Cavagnaro,

Prefix 9 is set on the trunk and i have also set the option [b]replace-prefix[/b] to remove it while passing out of Genesys. That is why when i dial 97050 from the Genesys workspace, the INVITE message is only passing 7050.

Correct me if i am wrong. And also, i have Genesys routing points starting with 7, so is it good to create a trunk with prefix 7?

Thank You
Best Regards