cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
13232
Views
0
Helpful
20
Replies

408 request timeout

uastac2011
Level 1
Level 1

Hi Guys


Need help. Cannot find the cause of the issue. Cannot make calls inbound and outbound.

Attached files are debugs and network topology. 

 

Thank you so much!

20 Replies 20

Hi 

Here is the current config.

 

bind control source-interface GigabitEthernet0/0/0
bind media source-interface GigabitEthernet0/0/0

was been added by the tac again.

Hi

The provider gave a reference for sip config. I added some config and disabled MTP in cucm and it is now ringing but actually it doesn't work.
Attached files are current config and debug.

Hi,

You are getting closer to the resolution. For outgoing calls, the CUBE Router is receiving "480 Temporarily Unavailable" message from Service Provider with warning message as ""The called num is invalid". Please check with your service provider about how many digits they are expecting over their network to complete the call successfully.

 

012180: Oct  2 16:43:16.036: //158267/88C740000000/SIP/Msg/ccsipDisplayMsg:
Received: 
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 10.105.82.162:5060;branch=z9hG4bK6A2519
Call-ID: 5FA6B7FE-E42711E9-B303888C-5DAE5EDA@10.105.82.162
From: "0453091834"<sip:+63453091834@10.91.52.38>;tag=263A0391-13BF
To: <sip:6061834@10.91.52.38>;tag=hdcYGxKq
CSeq: 101 INVITE
Warning: 399 229.3086.1009.ATS.19.32082.hc5gtsats01.vims.globe.com.ph "The called num is invalid."
Reason: Q.850;cause=31;text="Normal, unspecified",SIP;cause=480
P-Charging-Function-Addresses: ccf=hc5gtsccf01.vims.globe.com.ph;ecf=hc5gtsccf01.vims.globe.com.ph;ccf=hc5lhgccf01.vims.globe.com.ph;ecf=hc5lhgccf01.vims.globe.com.ph
P-Charging-Vector: icid-value="ac780dc0c1eea094d78738721ba2e991.3778994537.16129389.51";orig-ioi=vims.globe.com.ph
Content-Length: 0

 

 

 

Please rate helpful posts and if applicable mark "Accept as a Solution".
Thanks, Vaijanath S.

As you are already using bind interface command under dial-peer, you don't need it under sip configuration:

voice service voip
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
supplementary-service media-renegotiate
sip
no bind control source-interface GigabitEthernet0/0/0
no bind media source-interface GigabitEthernet0/0/0
options-ping 60 
!

Your dial-peer 201 which is pointed to CUCM is configured with bind interface Gig0/0/0. You need to change this to Port-Channel 1 otherwise your incoming calls will not work. Update you dial-peer 201:

dial-peer voice 201 voip
description ** Outgoing From VG to CUCM **
destination-pattern 1830
session protocol sipv2
session target ipv4:192.168.3.10
session transport udp
voice-class codec 1 
voice-class sip bind control source-interface Port-channel1
voice-class sip bind media source-interface Port-channel1
dtmf-relay rtp-nte
!

The best practice is to leave VAD disabled on dial-peer or globally.
https://community.cisco.com/t5/telepresence-and-video/impact-of-vad/td-p/1544831 

dial-peer voice 100 voip
no vad
!
dial-peer voice 102 voip
no vad
!
dial-peer voice 200 voip
no vad
!
dial-peer voice 201 voip
no vad
!

Also, as you are using only one interface connecting to LAN, I do not see any reason for using Port-Channel.

 

Please rate helpful posts and if applicable mark "Accept as a Solution".
Thanks, Vaijanath S.

Hi Vaijanath
Outgoing calls is now working. I changed the called number to 10 digits.
Thank you so much

I am glad that your issue is resolved.

 

 

Please rate helpful posts and if applicable mark "Accept as a Solution".
Thanks, Vaijanath S.