SIP trunk CUCM 9 to Avaya IP office 500 v2 issues

[mendrika.andrianina]

Hi guys,

Pretty sure I followed all instructions here http://tinyurl.com/oq5hgn7 but when it comes to the test, I have calls from Avaya IPO to CUCM 9 working great but calls from CUCM 9 to Avaya IP Office don't work.

Have someone experienced it before?

[Nadeem Jan]

I am facing the same issue configuring a Sip trunk from call manager to avaya ip office but invite send from CUCM but not received at Avaya..logs of cucm is given below..Can you help from AVAYA side.

15:45:11.696 |//SIP/SIPTcp/wait_SdlReadRsp: Incoming SIP TCP message from 192.168.63.76 on port 50818 index 7072 with 1421 bytes:

[148891,NET]

INVITE sip:2016@192.168.33.4;user=phone SIP/2.0

Via: SIP/2.0/TCP 192.168.63.76:50818;branch=z9hG4bK07fa24ad

From: "2810" <sip:2810@192.168.33.4>;tag=dceb94cefeff00067f847817-06223b9d

To: <sip:2016@192.168.33.4>

Call-ID: dceb94ce-feff0004-39bbef38-0882aa54@192.168.63.76

Max-Forwards: 70

Date: Thu, 11 Feb 2016 10:45:10 GMT

CSeq: 101 INVITE

User-Agent: Cisco-CP7841/10.3.1

Contact: <sip:c5208caa-3385-765c-de1b-5871c78c9017@192.168.63.76:50818;transport=tcp>

Expires: 180

Accept: application/sdp

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

Remote-Party-ID: "2810" <sip:2810@192.168.33.4>;party=calling;id-type=subscriber;privacy=off;screen=yes

Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-7.0.0,X-cisco-xsi-8.5.1

Allow-Events: kpml,dialog

Content-Length: 351

Content-Type: application/sdp

Content-Disposition: session;handling=optional

v=0

o=Cisco-SIPUA 15185 0 IN IP4 192.168.63.76

s=SIP Call

t=0 0

m=audio 22018 RTP/AVP 9 0 8 116 18 101

c=IN IP4 192.168.63.76

a=rtpmap:9 G722/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:116 iLBC/8000

a=fmtp:116 mode=20

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=yes

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=sendrecv

|CallingPartyNumber=2810

|DialingPartition=

|DialingPattern=201X

|FullyQualifiedCalledPartyNumber=2016

15:45:11.715 |//SIP/SIPTcp/wait_SdlSPISignal: Outgoing SIP TCP message to 192.168.39.30 on port 5060 index 7073

[148893,NET]

INVITE sip:2016@192.168.39.30:5060 SIP/2.0

Via: SIP/2.0/TCP 192.168.33.4:5060;branch=z9hG4bKfd782ca618

From: <sip:2810@192.168.33.4>;tag=49391~0724933f-834e-40ea-a65f-5a5d274fd9df-46003885

To: <sip:2016@192.168.39.30>

Date: Thu, 11 Feb 2016 10:45:11 GMT

Call-ID: 85089b00-6bc16637-46-421a8c0@192.168.33.4

Supported: timer,resource-priority,replaces

Min-SE:  1800

User-Agent: Cisco-CUCM8.5

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

CSeq: 101 INVITE

Expires: 180

Allow-Events: presence

Supported: X-cisco-srtp-fallback

Supported: Geolocation

Cisco-Guid: 2231933696-0000065536-0000000002-0069314752

Session-Expires:  1800

P-Asserted-Identity: <sip:2810@192.168.33.4>

Remote-Party-ID: <sip:2810@192.168.33.4>;party=calling;screen=yes;privacy=off

Contact: <sip:2810@192.168.33.4:5060;transport=tcp>

Max-Forwards: 69

Content-Length: 0

[Vivek Batra]

Hi Nadeem,

If you can not figure out from Avaya side what is the issue, only option from CUCM side is to enable early offer (under SIP profile) in CUCM and see how it goes.

- Vivek

[Ayodeji Okanlawon]

If the INVITE is not seen at Avaya, then you have a different issue here.

You need to check network connectivity first. Is there a firewall between CUCM and Avaya?

[Vivek Batra]

Hi D, IMO there should not be network issue since INVITE is sent using TCP and if we can see INVITE in CUCM logs, that means TCP connection to Avaya has been established successfully which indicates that there should not be any routing related issue. Isn't it?

- Vivek

[Ayodeji Okanlawon]

Yes that is correct, since CUCM already establish a TCP connection before sending the INVITE. I didn't check what transport protocol it was using..Thanks (+5)

However if the INVITE doesn't arrive at Avaya, then it could still be a network issue such as firewall etc.

[Vivek Batra]

Hi D, I got to know from one of the source (I can not validate his information) that  if Avaya IPO receives INVITE without SDP offer, IPO SIP stack straight away ignores that message and doesn't give any event to application, hence logs might not be generated for the same.

Anyway, let see how the issue reporter responds further on this.

- Vivek

[Nadeem Jan]

Dear Vivek,

Could you please confirm that in the above logs SDP invite along with SIP early offer generated or not??