ALE OXE 12.2 SIP with AVAYA CM

[morio]

hi guys,
hope some one can shed some light on my problem. i have a site with public sip trunk intergrated and works fine. Ascom mobile sip trunk intergradtion that works fine and a PRI intergration with Cisco CM which works fine.
i have to intergrate a Avaya CM to this oxe via using sip trunk. i have issues with both incoming and out going.

01- out going calls to avaya. for out going calls i can call the avaya user. once the user answeres the call> oxe keeps on recieving 200 ok SDP but oxe never send ACK. so the call disconnects the out going call. (the wirechark trace 145 outgoingfrom oxe)

02- incoming calls from avaya. when avaya calls oxe. the call reaches the oxe but oxe sends 488 not acceptable here. (wireshark trace 145 incomingfrom avaya)

can some one advice on these issues. will be much appreciated.

thanks in advance

145 out goingfrom oxe.rar

145 incomingfrom avaya.rar

[haroun]

hi ! sincerly i was lost witjh your topology
0-1 first of all why oxe(10.10.42.10] send invite via port 10286 ?
when oxe send Prack and recieved 200 ok , it is normal that it will not answer to it , if someone can correct but Prack should be sent after 183 session pregress received message !! wich is not the case.
at the end of the session we can see cleary oxe responds to the bye message recieved on 5060 , we can see it again in the incoming call from avaya all signaling messages are sent received via 5060

[haroun]

incoming , try to deactive g729 offer , and see other red lightned
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:7900@moimsd.gov.sa SIP/2.0
Method: INVITE
Request-URI: sip:7900@moimsd.gov.sa
Request-URI User Part: 7900
Request-URI Host Part: moimsd.gov.sa
[Resent Packet: False]
Message Header
Route: <sip:10.10.42.10;transport=tcp;lr;phase=terminating;m-type=audio>
Route URI: sip:10.10.42.10;transport=tcp;lr;phase=terminating;m-type=audio
Route Host Part: 10.10.42.10
Route URI parameter: transport=tcp
Route URI parameter: lr
Route URI parameter: phase=terminating
Route URI parameter: m-type=audio
Max-Breadth: 60
P-Charging-Vector: icid-value="AAS:4431-8cd6394aec411863c004eb26ba24a29"
icid-value: "AAS:4431-8cd6394aec411863c004eb26ba24a29"
Session-Expires: 1200;refresher=uac
Record-Route: <sip:ryd-ipt-sip1@10.50.235.145;transport=tcp;lr;av-asset-uid=7efe733>
Record-Route URI: sip:ryd-ipt-sip1@10.50.235.145;transport=tcp;lr;av-asset-uid=7efe733
Record-Route Userinfo: ryd-ipt-sip1
Record-Route Host Part: 10.50.235.145
Record-Route URI parameter: transport=tcp
Record-Route URI parameter: lr
Record-Route URI parameter: av-asset-uid=7efe733
Record-Route: <sip:127.0.0.2:15060;transport=tcp;ibmsid=local.1640070104244_48997_49132;lr;ibmdrr>
Record-Route URI: sip:127.0.0.2:15060;transport=tcp;ibmsid=local.1640070104244_48997_49132;lr;ibmdrr
Record-Route Host Part: 127.0.0.2
Record-Route Host Port: 15060
Record-Route URI parameter: transport=tcp
Record-Route URI parameter: ibmsid=local.1640070104244_48997_49132
Record-Route URI parameter: lr
Record-Route URI parameter: ibmdrr
Record-Route: <sips:127.0.0.2:15061;ibmsid=local.1640070104244_48997_49132;lr;ibmdrr>
Record-Route URI: sips:127.0.0.2:15061;ibmsid=local.1640070104244_48997_49132;lr;ibmdrr
Record-Route Host Part: 127.0.0.2
Record-Route Host Port: 15061
Record-Route URI parameter: ibmsid=local.1640070104244_48997_49132
Record-Route URI parameter: lr
Record-Route URI parameter: ibmdrr
Record-Route: <sip:ryd-ipt-sip1@10.50.235.145;transport=tls;lr;av-asset-uid=7efe733>
Record-Route URI: sip:ryd-ipt-sip1@10.50.235.145;transport=tls;lr;av-asset-uid=7efe733
Record-Route Userinfo: ryd-ipt-sip1
Record-Route Host Part: 10.50.235.145
Record-Route URI parameter: transport=tls
Record-Route URI parameter: lr
Record-Route URI parameter: av-asset-uid=7efe733
Record-Route: <sip:10.50.235.140:5061;transport=tls;lr>
Record-Route URI: sip:10.50.235.140:5061;transport=tls;lr
Record-Route Host Part: 10.50.235.140
Record-Route Host Port: 5061
Record-Route URI parameter: transport=tls
Record-Route URI parameter: lr
Min-SE: 1200
Alert-Info: <cid:internal@moimsd.gov.sa>;avaya-cm-alert-type=internal
Accept-Language: en
Contact: "Sultan, M.Alsultan" <sip:+7564@10.50.235.140:5061;transport=tls;gsid=4a39d61e-6318-41ec-b24d-000c294aa26b;asm=1>
SIP C-URI display info: "Sultan, M.Alsultan"
Contact URI: sip:+7564@10.50.235.140:5061;transport=tls;gsid=4a39d61e-6318-41ec-b24d-000c294aa26b;asm=1
Contact URI User Part: +7564
E.164 number (MSISDN): 7564
Country Code: Russian Federation, Kazakstan (Republic of) (7)
Contact URI Host Part: 10.50.235.140
Contact URI Host Port: 5061
Contact URI parameter: transport=tls
Contact URI parameter: gsid=4a39d61e-6318-41ec-b24d-000c294aa26b
Contact URI parameter: asm=1
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY, REFER, INFO, PRACK, PUBLISH, UPDATE
Supported: 100rel, histinfo, join, replaces, sdp-anat, timer
Via: SIP/2.0/TCP 10.50.235.145;branch=z9hG4bK78382291350432-AP;ft=33
Transport: TCP
Sent-by Address: 10.50.235.145
Branch: z9hG4bK78382291350432-AP
ft=33
Via: SIP/2.0/TCP 127.0.0.2:15060;rport=25261;ibmsid=local.1640070104244_48998_49133;branch=z9hG4bK78382291350432
Transport: TCP
Sent-by Address: 127.0.0.2
Sent-by port: 15060
RPort: 25261
ibmsid=local.1640070104244_48998_49133
Branch: z9hG4bK78382291350432
Via: SIP/2.0/TCP 127.0.0.2:15060;rport;ibmsid=local.1640070104244_48997_49132;branch=z9hG4bK224094041846611
Transport: TCP
Sent-by Address: 127.0.0.2
Sent-by port: 15060
RPort: rport
ibmsid=local.1640070104244_48997_49132
Branch: z9hG4bK224094041846611
Via: SIP/2.0/TLS 10.50.235.145;branch=z9hG4bK4a39de3e631841ecb2510c294aa26b-AP;ft=18;received=10.50.235.145;rport=36435
Transport: TLS
Sent-by Address: 10.50.235.145
Branch: z9hG4bK4a39de3e631841ecb2510c294aa26b-AP
ft=18
Received: 10.50.235.145
RPort: 36435
Via: SIP/2.0/TLS 10.50.235.140;branch=z9hG4bK4a39de3e631841ecb2510c294aa26b
Transport: TLS
Sent-by Address: 10.50.235.140
Branch: z9hG4bK4a39de3e631841ecb2510c294aa26b
Via: SIP/2.0/TLS 10.50.233.52;branch=z9hG4bK4a39de3e631841ecb2510c294aa26b
Transport: TLS
Sent-by Address: 10.50.233.52
Branch: z9hG4bK4a39de3e631841ecb2510c294aa26b
User-Agent: Avaya CM/R018x.01.0.890.0 AVAYA-SM-8.1.3.3.813310
P-AV-Message-Id: 1_1
[Expert Info (Note/Undecoded): Unrecognised SIP header (p-av-message-id)]
[Unrecognised SIP header (p-av-message-id)]
[Severity level: Note]
[Group: Undecoded]
Call-ID: 4a39da42631841ecb2500c294aa26b
[Generated Call-ID: 4a39da42631841ecb2500c294aa26b]
Max-Forwards: 66
CSeq: 1 INVITE
Sequence Number: 1
Method: INVITE
Content-Type: application/sdp
Content-Length: 190
Av-Global-Session-ID: 4a39d61e-6318-41ec-b24d-000c294aa26b
[Expert Info (Note/Undecoded): Unrecognised SIP header (av-global-session-id)]
[Unrecognised SIP header (av-global-session-id)]
[Severity level: Note]
[Group: Undecoded]
P-Location: SM;origlocname="Riyadh";origsiglocname="Riyadh";origmedialocname="Riyadh";termlocname="Riyadh";termsiglocname="Riyadh";smaccounting="true"
[Expert Info (Note/Undecoded): Unrecognised SIP header (p-location)]
[Unrecognised SIP header (p-location)]
[Severity level: Note]
[Group: Undecoded]
To: <sip:7900@moimsd.gov.sa>
SIP to address: sip:7900@moimsd.gov.sa
SIP to address User Part: 7900
SIP to address Host Part: moimsd.gov.sa
P-Asserted-Identity: "Sultan, M.Alsultan" <sip:7564@moimsd.gov.sa>
SIP PAI display info: "Sultan, M.Alsultan"
SIP PAI Address: sip:7564@moimsd.gov.sa
SIP PAI User Part: 7564
SIP PAI Host Part: moimsd.gov.sa
From: "Sultan, M.Alsultan" <sip:7564@moimsd.gov.sa>;tag=4a39da2e631841ecb24f0c294aa26b
SIP from display info: "Sultan, M.Alsultan"
SIP from address: sip:7564@moimsd.gov.sa
SIP from address User Part: 7564
SIP from address Host Part: moimsd.gov.sa
SIP from tag: 4a39da2e631841ecb24f0c294aa26b
History-Info: <sip:7900@moimsd.gov.sa>;index=1, "667900" <sip:7900@moimsd.gov.sa>;index=1.1
<sip:7900@moimsd.gov.sa>;index=1
"667900" <sip:7900@moimsd.gov.sa>;index=1.1
Message Body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 1640171651 1 IN IP4 10.50.235.140
Owner Username: -
Session ID: 1640171651
Session Version: 1
Owner Network Type: IN
Owner Address Type: IP4
Owner Address: 10.50.235.140
Session Name (s): -
Connection Information (c): IN IP4 10.50.235.148
Connection Network Type: IN
Connection Address Type: IP4
Connection Address: 10.50.235.148
Bandwidth Information (b): AS:64
Bandwidth Modifier: AS [Application Specific (RTP session bandwidth)]
Bandwidth Value: 64 kb/s
Time Description, active time (t): 0 0
Session Start Time: 0
Session Stop Time: 0
Media Description, name and address (m): audio 2052 RTP/AVP 0 18 8 127
Media Type: audio
Media Port: 2052
Media Protocol: RTP/AVP
Media Format: ITU-T G.711 PCMU
Media Format: ITU-T G.729
Media Format: ITU-T G.711 PCMA
Media Format: DynamicRTP-Type-127
Media Attribute (a): sendrecv
Media Attribute (a): fmtp:18 annexb=no
Media Attribute Fieldname: fmtp
Media Format: 18 [Unknown]
Media format specific parameters: annexb=no
Media Attribute (a): rtpmap:127 telephone-event/8000
Media Attribute Fieldname: rtpmap
Media Format: 127
MIME Type: telephone-event
Sample Rate: 8000
[Generated Call-ID: 4a39da42631841ecb2500c294aa26b]

IBM-PO: 0
[Expert Info (Note/Undecoded): Unrecognised SIP header (ibm-po)]
[Unrecognised SIP header (ibm-po)]
[Severity level: Note]
[Group: Undecoded]
Content-Length: 0

[morio]

hi ! sincerly i was lost witjh your topology
0-1 first of all why oxe(10.10.42.10] send invite via port 10286 ?
when oxe send Prack and recieved 200 ok , it is normal that it will not answer to it , if someone can correct but Prack should be sent after 183 session pregress received message !! wich is not the case.
at the end of the session we can see cleary oxe responds to the bye message recieved on 5060 , we can see it again in the incoming call from avaya all signaling messages are sent received via 5060

thnks on your feed back. sorry if my explanations was little bit scrappy. i will check on your comments with the system and let you know. yes as you said i noticed with other sip providers the oxe sends with port 5060. but not to avaya. i will check whats the reason for than first and check on my issue 2.
thanks again.

[morio]

hi ! sincerly i was lost witjh your topology
0-1 first of all why oxe(10.10.42.10] send invite via port 10286 ?
when oxe send Prack and recieved 200 ok , it is normal that it will not answer to it , if someone can correct but Prack should be sent after 183 session pregress received message !! wich is not the case.
at the end of the session we can see cleary oxe responds to the bye message recieved on 5060 , we can see it again in the incoming call from avaya all signaling messages are sent received via 5060

thnks on your feed back. sorry if my explanations was little bit scrappy. i will check on your comments with the system and let you know. yes as you said i noticed with other sip providers the oxe sends with port 5060. but not to avaya. i will check whats the reason for than first and check on my issue 2.
thanks again.

hi, i checked and the cause is due that the external gate way for avaya use TCP only. if i modify if to UDP oxe will send sipport 5060. but not in TCP. im not much understanding in UDP and TCP, i hope there isa reasonable explanation for this behaviour ...

[morio]

hi all,
i am attaching a nother trace. oxe ip 10.10.42.10 avaya 10.50.235.140. this is the same oxe of the other two traces. but deferent avaya cm. gate way parameters are the same. but out going works well on this trace (10.50.235.140) while other destination (10.50.235.145) disconnected after 30 seconds as oxe dont send ACK.
BUT WHY,,,

[haroun]

hi
can u pas t the oxe internal sip Gateway and th evaya external Gateway config at oxe side
btw i see that oxe send ack after after200ok from avaya

[morio]

hi
can u pas t the oxe internal sip Gateway and th evaya external Gateway config at oxe side
btw i see that oxe send ack after after200ok from avaya

hi haroun, thanks for your interest on this, i will post the gate way set up and also the mao back up for your referance.. thanks again.

[haroun]

please upload only internal sipgateway , not all mao backup i have not a lab for test

[morio]

Consult/Modify: External Gateways────────────────────────────────────────────────────────┐
│ │
│ Node Number (reserved) : 1 │
│ Instance (reserved) : 1 │
│ Instance : 9 │
│ │
│ Gateway Name : MF AVYA │
│ Remote domain : 10.50.235.140 │
│ PCS IP address : ----------------------------------------------- │
│ Port number : 5060 │
│ Transport type + TCP │
│ Belonging domain : moimsd.gov.sa │
│ Registration ID : -------------------------------------------------- │
│ Registration ID in P_Asserted + True │
│ Registration timer : 0 │
│ Outbound Proxy : -------------------------------------------------- │
│ Supervision timer : 0 │
│ Trunk group number : 421 │
│ Pool Number : -1 │
│ Outgoing realm : -------------------------------------------------- │
│ Outgoing username : -------------------------------------------------- │
│ │
│ Outgoing Password : -------------------- │
│ Confirm : -------------------- │
│ │
│ Incoming username : -------------------------------------------------- │
│ │
│ Incoming Password : --------------------
│
│ Confirm : -------------------- │
│ │
│ RFC 3325 supported by the distant + True │
│ DNS type + DNS A │
│ First DNS IP Address : ----------------------------------------------- │
│ Second DNS IP Address : ----------------------------------------------- │
│ SDP in 18x + False │
│ Minimal authentication method + None │
│ INFO method for remote extension + True │
│ To EMS + False │
│ SRTP + RTP only │
│ Ignore inactive/black hole + True │
│ Contact with IP address + False │
│ Dynamic Payload type for DTMF : 97 │
│ Outbound Calls 100 REL + Supported │
│ Incoming Calls 100 REL + Required Mode1 │
│ Gateway type + Standard type │
│ Re-Trans No. for REGISTER/OPTIONS : 2 │
│ P-Asserted-ID in Calling Number + True │
│ Trusted P-Asserted-ID header + True │
│ Diversion Info to provide via + History Info │
│ Proxy identification on IP address + False │
│ Outbound calls only + False │
│ SDP relay on Ext. Call Fwd + Default │
│ SDP Transparency Override + False │
│ RFC 5009 supported / Outbound call + Not Supported
│ Nonce caching activation + NO │
│ FAX Procedure Type + T38 only │
│ DNS SRV/Call retry on busy server : 0 │
│ Unattended Transfer for RSI + NO │
│ Redirection functionality + NO │
│ Attended Transfer + NO │
│ Send BYE on REFER + YES │
│ Redirection response support + NO │
│ OPTIONS required + YES │
│ Support UTF8 characters set + NO │
│ CSTA User-to-User supported + NO │
│ DDI destination number + ReqURI │
│ Video Support Profile + Not Supported │
│ UPDATE in Allow header/INVITE + Optional │
│ RFC 4904 supported + NO │
│ Bulk registration (RFC 6140) + NO │
│ RFC3264 m-line + True │
│ Sendonly for hold + False │
│ In Band DTMF + NO │
│ Trusted From header + False │
│ Support Re-invite without SDP + True │
│ Type of codec negotiation + Single codec G711