02-16-2015 01:16 PM - edited 03-17-2019 02:00 AM
Greetings,
The issue i am facing is that I cannot hear ringback whenever dialing any Mobile Numbers. I informed my provider regarding the said issue and he asked me that why am I not sending any Media negotiations parameters in an invite message. I've already configured it under voice service voip.
Topology:- CUCM ---H323---CUBE---SIP Trunk---ITSP
ATTACHED LOGS :-
debug ccsip messages
debug voip ccapi inout
debug voip dialpeer inout
Regards
Solved! Go to Solution.
02-16-2015 02:20 PM
To be honest, if you want to make your life a little bit easier, and to avoid compatibility issues. change protocol between CUCM and gwateway to SIP.
You would probably need to enable H323 fast start on the CUCM and H323 end of your gateway to cater to the early offer that your provider is sending you.
I have gone through similar headaches in the past and moved to SIP:
http://ciscoshizzle.blogspot.com.au/2012/12/sip-early-offer-cucm-trunk.html
02-16-2015 01:22 PM
Please post the full debug ccsip messages
02-16-2015 01:48 PM
Also post your voice service voip
02-16-2015 02:06 PM
voice service voip
ip address trusted list
ipv4 0.0.0.0 0.0.0.0
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
supplementary-service h450.12
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
h323
emptycapability
h225 signal overlap
h225 h245-address on-connect
h225 id-passthru
h225 connect-passthru
session transport udp
h245 passthru tcsnonstd-passthru
sip
bind control source-interface GigabitEthernet0/1
bind media source-interface GigabitEthernet0/1
listen-port non-secure 5083
early-offer forced
midcall-signaling passthru
no call service stop
02-16-2015 02:17 PM
I would also recommend sip trunk between cucm and cube instead of h323, that throws a wrench in the mix. I don't see "ringing" in the debug, just goes from Trying to OK to BYE with normal call clearing, although it may just be the debug is cut short.
Ringback is almost always an MTP issue in my experience though
02-16-2015 03:05 PM
Thats what is the issue. I am not seeing any Ringing from the ITSP side. I tried to configure SIP however there is some socket error.
All calls are connected to ITSP on 5083 port.
Log Buffer (10000000 bytes):
001277: Feb 17 04:02:32.532: TCP0: FIN processed
001278: Feb 17 04:02:32.532: TCP0: state was FINWAIT2 -> TIMEWAIT [56976 -> 192.
168.100.240(49)]
001279: Feb 17 04:02:33.852: TCB3E7DD4D8 created
001280: Feb 17 04:02:33.852: TCP0: state was LISTEN -> SYNRCVD [443 -> 10.99.32.
2(55574)]
001281: Feb 17 04:02:33.852: TCP: tcb 3E7DD4D8 connection to 10.99.32.2:55574, p
eer MSS 1460, MSS is 516
001282: Feb 17 04:02:33.852: TCP: Selective ack is disabled from the CLI
001283: Feb 17 04:02:33.852: TCP: sending SYN, seq 3523819021, ack 3123190603
001284: Feb 17 04:02:33.852: TCP0: Connection to 10.99.32.2:55574, advertising M
SS 536
001285: Feb 17 04:02:33.872: TCP0: state was SYNRCVD -> ESTAB [443 -> 10.99.32.2
(55574)]
001286: Feb 17 04:02:33.872: TCB236C51D4 accepting 3E7DD4D8 from 10.99.32.2.5557
4
001287: Feb 17 04:02:33.872: TCB3E7DD4D8 setting property TCP_NO_DELAY (0) 3CC71
254
001288: Feb 17 04:02:33.872: TCB3E7DD4D8 setting property TCP_NONBLOCKING_WRITE
(10) 3CC71344
001289: Feb 17 04:02:33.872: TCB3E7DD4D8 setting property TCP_NONBLOCKING_READ (
14) 3CC71344
001290: Feb 17 04:02:33.872: TCB3E7DD4D8 setting property TCP_KEEPALIVE (17) 3CC
71344
001291: Feb 17 04:02:33.872: TCP: Setting Keepalive interval and retries to 60 a
nd 4
001292: Feb 17 04:02:34.328: TCP0: ACK timeout timer expired
001293: Feb 17 04:02:34.364: TCB3E7DD4D8 shutdown writing
001294: Feb 17 04:02:34.364: TCP0: state was ESTAB -> FINWAIT1 [443 -> 10.99.32.
2(55574)]
001295: Feb 17 04:02:34.364: TCP0: sending FIN
001296: Feb 17 04:02:34.384: TCP0: FIN processed
001297: Feb 17 04:02:34.384: TCP0: state was FINWAIT1 -> CLOSING [443 -> 10.99.3
2.2(55574)]
001298: Feb 17 04:02:34.384: TCP0: RST received, Closing connection
001299: Feb 17 04:02:34.384: TCP0: state was CLOSING -> CLOSED [443 -> 10.99.32.
2(55574)]
001300: Feb 17 04:02:34.384: TCB 0x3E7DD4D8 destroyed
001301: Feb 17 04:02:37.788: TCB3E7DD4D8 created
001302: Feb 17 04:02:37.788: TCP0: state was LISTEN -> SYNRCVD [5083 -> 10.200.1
5.20(33447)]
001303: Feb 17 04:02:37.788: TCP: tcb 3E7DD4D8 connection to 10.200.15.20:33447,
peer MSS 1460, MSS is 516
001304: Feb 17 04:02:37.788: TCP: Selective ack is disabled from the CLI
001305: Feb 17 04:02:37.788: TCP: sending SYN, seq 1375843679, ack 3851572463
001306: Feb 17 04:02:37.788: TCP0: Connection to 10.200.15.20:33447, advertising
MSS 536
001307: Feb 17 04:02:37.792: TCP0: state was SYNRCVD -> ESTAB [5083 -> 10.200.15
.20(33447)]
001308: Feb 17 04:02:37.792: TCB3DD71E8C accepting 3E7DD4D8 from 10.200.15.20.33
447
001309: Feb 17 04:02:37.792: TCB3E7DD4D8 setting property TCP_NO_DELAY (0) 232FB
BBC
001310: Feb 17 04:02:37.792: TCB3E7DD4D8 setting property TCP_NONBLOCKING_WRITE
(10) 232FBBFC
001311: Feb 17 04:02:37.792: TCB3E7DD4D8 setting property TCP_NONBLOCKING_READ (
14) 232FBBFC
001312: Feb 17 04:02:37.792: TCB3E7DD4D8 setting property TCP_NO_DELAY (0) 232FB
BFC
001313: Feb 17 04:02:37.792: TCB3E7DD4D8 setting property TCP_KEEPALIVE (17) 232
FBBFC
001314: Feb 17 04:02:37.792: TCP: Setting Keepalive interval and retries to 60 a
nd 4
001315: Feb 17 04:02:37.792: TCB3E7DD4D8 setting property TCP_ALWAYSPUSH (15) 23
2FBBFC
001316: Feb 17 04:02:37.800: TCB3E80AFA4 created
001317: Feb 17 04:02:37.800: TCB3E80AFA4 setting property TCP_NO_DELAY (0) 232FB
BC4
001318: Feb 17 04:02:37.800: TCB3E80AFA4 setting property TCP_NONBLOCKING_WRITE
(10) 232FBBF4
001319: Feb 17 04:02:37.800: TCB3E80AFA4 setting property TCP_NONBLOCKING_READ (
14) 232FBBF4
001320: Feb 17 04:02:37.800: TCB3E80AFA4 setting property TCP_NO_DELAY (0) 232FB
BF4
001321: Feb 17 04:02:37.800: TCB3E80AFA4 setting property TCP_KEEPALIVE (17) 232
FBBF4
001322: Feb 17 04:02:37.800: TCP: Setting Keepalive interval and retries to 60 a
nd 4
001323: Feb 17 04:02:37.800: TCB3E80AFA4 setting property TCP_ALWAYSPUSH (15) 23
2FBBF4
001324: Feb 17 04:02:37.800: TCP: Random local port generated 43468, network 1
001325: Feb 17 04:02:37.800: TCB3E80AFA4 bound to 10.99.1.23.43468
001326: Feb 17 04:02:37.800: Reserved port 43468 in Transport Port Agent for TCP
IP type 1
001327: Feb 17 04:02:37.800: TCP: sending SYN, seq 1653588689, ack 0
001328: Feb 17 04:02:37.800: TCP0: Connection to 10.200.15.20:5060, advertising
MSS 536
001329: Feb 17 04:02:37.800: TCP0: state was CLOSED -> SYNSENT [43468 -> 10.200.
15.20(5060)]
001330: Feb 17 04:02:37.992: TCP0: ACK timeout timer expired
001331: Feb 17 04:02:39.800: 10.99.1.23:43468 <---> 10.200.15.20:5060 congesti
on window changes
001332: Feb 17 04:02:39.800: cwnd from 536 to 536, ssthresh from 65535 to 1072
001333: Feb 17 04:02:39.800: TCP0: timeout #1 - timeout is 4000 ms, seq 16535886
89
001334: Feb 17 04:02:39.800: TCP: (43468) -> 10.200.15.20(5060)
001335: Feb 17 04:02:42.796: %VOICE_IEC-3-GW: SIP: Internal Error (Socket error)
: IEC=1.1.186.7.7.5 on callID 13 GUID=E4FE6A000001000000000895140FC80A
001336: Feb 17 04:02:42.796: Released port 43468 in Transport Port Agent for TCP
IP type 1 delay 240000
001337: Feb 17 04:02:42.796: TCP0: state was SYNSENT -> CLOSED [43468 -> 10.200.
15.20(5060)]
001338: Feb 17 04:02:42.796: TCB 0x3E80AFA4 destroyed
001339: Feb 17 04:02:47.508: TCB2260EF40 created
001340: Feb 17 04:02:47.508: TCB2260EF40 setting property TCP_GIVEUP (41) 3B6559
7C
001341: Feb 17 04:02:47.508: TCP: Random local port generated 49300, network 1
001342: Feb 17 04:02:47.508: TCB2260EF40 bound to 10.200.100.27.49300
001343: Feb 17 04:02:47.508: Reserved port 49300 in Transport Port Agent for TCP
IP type 1
001344: Feb 17 04:02:47.508: TCP: sending SYN, seq 2603559115, ack 0
001345: Feb 17 04:02:47.508: TCP0: Connection to 192.168.100.240:49, advertising
MSS 536
001346: Feb 17 04:02:47.508: TCP0: state was CLOSED -> SYNSENT [49300 -> 192.168
.100.240(49)]
001347: Feb 17 04:02:47.508: TCP0: state was SYNSENT -> ESTAB [49300 -> 192.168.
100.240(49)]
001348: Feb 17 04:02:47.508: TCP: tcb 2260EF40 connection to 192.168.100.240:49,
peer MSS 1460, MSS is 536
001349: Feb 17 04:02:47.508: TCB2260EF40 connected to 192.168.100.240.49
001350: Feb 17 04:02:47.708: TCP0: state was ESTAB -> FINWAIT1 [49300 -> 192.168
.100.240(49)]
001351: Feb 17 04:02:47.708: TCP0: sending FIN
02-17-2015 02:09 AM
Looks like there is connectivity issue between the CUBE and CUCM (10.200.15.20) on port 5060
10.99.1.23:43468 <---> 10.200.15.20:5060
001337: Feb 17 04:02:42.796: TCP0: state was SYNSENT -> CLOSED [43468 -> 10.200.
15.20(5060)]
Is the ip 10.200.15.20 reachable from the interface 10.99.1.23?
Is there a firewall between these two devices?
Can you send your sh run?
02-18-2015 10:32 AM
02-18-2015 03:45 PM
So what is the issue still? You said calls are working fine. Do you still have sip connectivity issues?
02-18-2015 08:26 PM
Sip Calls are working fine now. I need some advice regarding Unity express which is installed on 2901 Router.
I've some extensions on CME and some extensions on CUCM. What can i do in order to make sure that Unity will transfer calls to DN's which are configured on CME.
CTI Route Point is configured on CUCM.
CUCM --- H323 --- CUBE --- Sip Trunk --- ITSP
|
|
Sip Trunk
|
|
CME
02-16-2015 02:08 PM
I've attached the complete debugs.
02-16-2015 02:20 PM
To be honest, if you want to make your life a little bit easier, and to avoid compatibility issues. change protocol between CUCM and gwateway to SIP.
You would probably need to enable H323 fast start on the CUCM and H323 end of your gateway to cater to the early offer that your provider is sending you.
I have gone through similar headaches in the past and moved to SIP:
http://ciscoshizzle.blogspot.com.au/2012/12/sip-early-offer-cucm-trunk.html
02-17-2015 01:38 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide