CUCM vs CUBE SIP Messages

[JustForVoice_2]

Hello,

Is there any difference between CUCM and CUBE SIP messages? I tried to integrate Paging system (supports SIP) with our IPT solution. First I tried the following call flow:

CUCM => SIP Trunk => CUBE => SIP => Paging System

When I dial from IP phone, it keeps ringing and no answer. (Should open immediately and page)

Once I changed the IP address of the SIP trunk in CUCM to the paging system IP address, it worked.

But the customer requirement to keep the integration through the CUBE. Could you please help?

Regards,

[Vivek Batra]

Please share the output of debug ccsip messages of failed call.

[JustForVoice_2]

Kindly find the logs

10.10.10.100 CUCM

192.168.1.6 CUBE

192.168.1.222 Paging

IP Phone ext: 200

Paging Ext: 170

[Vivek Batra]

10.11.3.220, where this IP is assigned?

Did you take complete logs? I can not see logs after paging server sends 200 ok.

Can you also share the traces of working call?

[JustForVoice_2]

This is another IP in the PAGING, and no changes from Paging side.

All what I did is changing the IP Address in CUCM from CUBE to paging.

[JustForVoice_2]

Hello,

Sorry, to reply late. Today I was able to meet with Paging system team to work on the integration.

All, what I did today is to change the IP address in the dial-peer to point to the address that I saw in contact header. Everything is OK now.  

Before the OK message was:

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.6:5060;branch=z9hG4bK482022;received=192.168.1.6
From: <sip:200@192.168.1.6>;tag=B9CFE4E0-145
To: <sip:111@192.168.1.222>;tag=as7872fa82
Call-ID: 2E7DB3D1-BDE411E5-9388A668-FAC54363@192.168.1.6
CSeq: 101 INVITE
Server: Asterisk PBX 1.6.2.24
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Contact: <sip:111@192.168.1.220>
Content-Type: application/sdp
Content-Length: 228

Then I adjust the dial-peer to point to 192.168.1.220 rather than .222

But my question is why CUCM accept this while CUBE no?

[JustForVoice_2]

I attached an image to show the call flow.

Any one can tell me if the call flow is right?

[Ayodeji Okanlawon]

The log is not complete. We do not see the CUBE sending 200 OK back to cucm.

First of all we need to change the sip transport protocol to ensure we use the same protocol for the whole call. Currently we have cucm using TCP and CUBE using UDP.

Lets try this

1.configure the dial-peer facing the paging system to use tcp as the transport protocol

dial-peer voice xxx voip

session transport tcp

Test again and send us debug ccsip messages

[JustForVoice_2]

Thank you too much +5

Could you please share with me other possibilities?

I left the site and I will try tomorrow, so I can try more than one option.

[Ayodeji Okanlawon]

We can only proceed once we see the logs. So please get in touch tomorrow when you are onsite and hopefully we can resolve this.

[JustForVoice_2]

I forgot to say that I saw the following message from CUBE to CUCM after keep ringing for long time:

Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP 10.10.10.100:5060;branch=z9hG4bK5ffd8243cae75
From: "Paging Test" <sip:200@10.10.10.100>;tag=769323~680d56b4-4710-48e9-ba27-660f9e697be4-142047552
To: <sip:170@192.168.1.6>;tag=9B696E68-C82
Date: Wed, 13 Jan 2016 15:25:12 GMT
Call-ID: e737180-69616cb8-5db23-36c9200a@10.10.10.100
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.5.1.T2
Reason: Q.850;cause=16
Content-Length: 0

[Ayodeji Okanlawon]

It was ringing for a long time because the sip messages were not complete. Hopefully we can find a solution tomorrow