Change CUCM SIP turnk "session version" 1

Unanswered Question
Jan 29th, 2014
User Badges:

Hi everybody,


Here is the call flow

External phone --- PSTN --- VG --- CUCM --- 3rd party system

Case #1

Previously, I was using a CUCM9 (only publisher) e.g. 10.10.10.55

and create a SIP trunk that connect to other system

The external phone can successfully reach the 3rd party system

Case #2

Then I build another CUCM9 with (Publisher and Subscriber) e.g. 10.10.10.7 and 10.10.10.8

And created the same SIP trunk that connect to other system

The external phone FAIL to reach the 3rd party system ....

I tried to use wireshark and see the SIP INVITE and ACK information

and find that ...


In Case #1, call SUCCESS

the "Media Terminiation Point Required" is checked in "SIP Trunk"

result:

SIP "Session Version" is 1

"Connection Information (c): IN IP4 10.10.10.55

###################################

in Case #2,

call FAIL


Setting #A:

- checked "Media Terminiation Point Required" in "SIP Trunk"

- unchecked "Early Offer support for voice and video calls (insert MTP if needed)" in "SIP Profile"


Result #A:

SIP "session version" is 2

"Connection Information (c): IN IP4 0.0.0.0

=======================================================================

Setting #B:

- unchecked "Media Terminiation Point Required" in "SIP Trunk"

- checked "Early Offer support for voice and video calls (insert MTP if needed)" in "SIP Profile"

Result #B:

SIP "session version" is 2

"Connection Information (c): IN IP4 10.10.10.7



========================================================================

Setting #C:

- unchecked "Media Terminiation Point Required" in "SIP Trunk"

- unchecked "Early Offer support for voice and video calls (insert MTP if needed)" in "SIP Profile"

Result #C:

SIP "session version" is 1

"Connection Information (c): IN IP4 0.0.0.0



=======================================

The question is


Is it possible to make the result to

SIP "session version" is 1

"Connection Information (c): IN IP4 10.10.10.7


Thanks

Sam

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Manish Prasad Thu, 01/30/2014 - 00:50
User Badges:

Hi Sam,


IN IP4 0.0.0.0 - This happens when there is no binding in place.


If you think session version is the reason why calls are failing then there is always an option to modify SDP parameters using SIP Normalization Script - http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/sip_tn/8_5_1/4-sdp_api.html


Here is small clip from SDP rfc.


    is a version number for this session description.  Its
      usage is up to the creating tool, so long as  is
      increased when a modification is made to the session data.  Again,
      it is RECOMMENDED that an NTP format timestamp is used.


Thanks

Manish



Ayodeji Okanlawon Thu, 01/30/2014 - 02:24
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

I suggest you loot at things in detail and not make assumptions. Your best bet is to collect CUCM traces (SDL traces for cucm9) and examine the cause of the failure....You can attach teh trace here and we can look at it for you...include calling, called and time of call


Please rate all useful posts

"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"

Actions

This Discussion

Related Content