cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1677
Views
5
Helpful
2
Replies

3rd Party SIP Phone incoming call issue

LalitArora89
Level 1
Level 1

Hi all

 

i have registered Avaya 9611 & 9641 IP phone to CUCM 11.5

 

below is the issue summary.

 

whenever avaya phone tries to reach  Cisco IP phone on same call manager it able to make outbound call however when  Cisco phone try to reach same avaya phone it disconnect after ~40seconds and avaya phone didnt ring.

 

as per logs i could see erro 408 request timeout.

 

can anybody help me on this?

 

attaching logs.

Regards

Lalit Arora

2 Accepted Solutions

Accepted Solutions

LalitArora89
Level 1
Level 1

Noticed that the Alert-Info Header is causing the problem, part of the INVITE message being sent out to AVAYA Phone (Third Party SIP device in my case).

 

Alert-Info: <file://Bellcore-dr1/>

 

1. Configured a SIP Normalization Script to remove the Alert-Info Header from the INVITE message.

2. Applied the Normalization script to a SIP Profile.

3. Applied the SIP Profile to the Avaya Phone.

4. Test calls were successful both-sided with proper 2-way audio communication.

 

 

View solution in original post

 

Remove Alert info header from SIP invite from cisco to avaya..

 

image1.jpg

 

 

 

 

00488629.001 |04:11:55.670 |AppInfo  |SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 192.168.16.75 on port 3438 index 854

[27101,NET]

INVITE sip:1214@192.168.16.75:3438;transport=tcp;avaya-sc-enabled SIP/2.0

Via: SIP/2.0/TCP 192.168.16.101:5060;branch=z9hG4bKc31135f3c8

From: <sip:2002@192.168.16.101>;tag=9020~9aafa914-4115-4ccf-8a6e-e11e17c4aabc-32432700

To: <sip:1214@192.168.16.101>

Date: Mon, 18 Sep 2017 11:11:55 GMT

Call-ID: 2cbf5500-9bf1a9fb-ae-6510a8c0@192.168.16.101

Supported: timer,resource-priority,replaces

Min-SE:  1800

User-Agent: Cisco-CP9971/9.4.2

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY

CSeq: 101 INVITE

Expires: 180

Allow-Events: presence

Send-Info: conference, x-cisco-conference

Alert-Info: <file://Bellcore-dr1/>

Session-ID: 43b2d1ab923ac67a51a982a283aa9019;remote=00000000000000000000000000000000

Remote-Party-ID: <sip:2002@192.168.16.101;x-cisco-callback-number=2002>;party=calling;screen=yes;privacy=off

Contact: <sip:2002@192.168.16.101:5060;transport=tcp>

Max-Forwards: 69

Content-Type: application/sdp

Content-Length: 204

 

v=0

o=CiscoSystemsCCM-SIP 9020 1 IN IP4 192.168.16.101

s=SIP Call

c=IN IP4 192.168.16.101

t=0 0

m=audio 24608 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

 

00488630.000

Source Filename: SDL001_100_000026.txt

View solution in original post

2 Replies 2

LalitArora89
Level 1
Level 1

Noticed that the Alert-Info Header is causing the problem, part of the INVITE message being sent out to AVAYA Phone (Third Party SIP device in my case).

 

Alert-Info: <file://Bellcore-dr1/>

 

1. Configured a SIP Normalization Script to remove the Alert-Info Header from the INVITE message.

2. Applied the Normalization script to a SIP Profile.

3. Applied the SIP Profile to the Avaya Phone.

4. Test calls were successful both-sided with proper 2-way audio communication.

 

 

 

Remove Alert info header from SIP invite from cisco to avaya..

 

image1.jpg

 

 

 

 

00488629.001 |04:11:55.670 |AppInfo  |SIPTcp - wait_SdlSPISignal: Outgoing SIP TCP message to 192.168.16.75 on port 3438 index 854

[27101,NET]

INVITE sip:1214@192.168.16.75:3438;transport=tcp;avaya-sc-enabled SIP/2.0

Via: SIP/2.0/TCP 192.168.16.101:5060;branch=z9hG4bKc31135f3c8

From: <sip:2002@192.168.16.101>;tag=9020~9aafa914-4115-4ccf-8a6e-e11e17c4aabc-32432700

To: <sip:1214@192.168.16.101>

Date: Mon, 18 Sep 2017 11:11:55 GMT

Call-ID: 2cbf5500-9bf1a9fb-ae-6510a8c0@192.168.16.101

Supported: timer,resource-priority,replaces

Min-SE:  1800

User-Agent: Cisco-CP9971/9.4.2

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY

CSeq: 101 INVITE

Expires: 180

Allow-Events: presence

Send-Info: conference, x-cisco-conference

Alert-Info: <file://Bellcore-dr1/>

Session-ID: 43b2d1ab923ac67a51a982a283aa9019;remote=00000000000000000000000000000000

Remote-Party-ID: <sip:2002@192.168.16.101;x-cisco-callback-number=2002>;party=calling;screen=yes;privacy=off

Contact: <sip:2002@192.168.16.101:5060;transport=tcp>

Max-Forwards: 69

Content-Type: application/sdp

Content-Length: 204

 

v=0

o=CiscoSystemsCCM-SIP 9020 1 IN IP4 192.168.16.101

s=SIP Call

c=IN IP4 192.168.16.101

t=0 0

m=audio 24608 RTP/AVP 8 101

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

 

00488630.000

Source Filename: SDL001_100_000026.txt