Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1326
Views
5
Helpful
6
Replies

CUBE outgoing calls through SIP ITSP

ArnoldKern
Level 1
Level 1

‎08-19-2020 07:26 AM - edited ‎08-20-2020 01:48 AM

Hello colleagues.

I have a problem with the outgoing calls through CUBE
Scheme:
CUCM ---- SIP ---- CUBE ---- SIP ---- Provider

When I do incoming calls everything works fine.
When I do outgoing calls, provider send the SIP/2.0 401 Unauthorized towards CUBE and nothing happens after.

Sent:
INVITE sip:004115753388886@cisco.com:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.250.116:5060;branch=z9hG4bKF285F
From: <sip:134457300@cisco.com>
To: <sip:004115753388886@cisco.com>
Date: Wed, 19 Aug 2020 10:11:37 GMT
Call-ID: 3332F726-E13B11EA-8128A4FA-4D0338DC@192.168.250.116
Supported: timer,resource-priority,replaces,sdp-anat
Cisco-Guid: 3278553472-0000065536-0000732723-0520557578

User-Agent: Cisco-SIPGateway/IOS-16.9.5
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1597831897
Contact: <sip:124457399@192.168.250.116:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 68
P-Asserted-Identity: <sip:124457399@cisco.com>
Privacy: none
Session-Expires:  1800
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 278
v=0
o=CiscoSystemsSIP-GW-UserAgent 6442 9830 IN IP4 192.168.250.116
s=SIP Call
t=0 0
m=audio 8006 RTP/AVP 8 101 100
c=IN IP4 192.168.250.116
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=ptime:20

Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.250.116:5060;received=185.233.25.84;branch=z9hG4bKF285F;rport=54108
From: <sip:134457300@cisco.com>
To: <sip:004115753388886@cisco.com>;tag=SD4re3c99-1824414296-1597831640951
Call-ID: 3332F726-E13B11EA-8128A4FA-4D0338DC@192.168.250.116
CSeq: 101 INVITE
Timestamp: 1597831896
WWW-Authenticate: DIGEST
qop="auth",nonce="BroadWorksXke17pconTz7yjljBW",realm="cisco.com",algorithm=MD5
Content-Length: 0“


Could the tag (see in red) be the source of the problem?

0 Helpful
6 Replies 6

davisjaron
Level 1
Level 1

‎08-19-2020 07:56 AM

A common reason calls would be rejected like that is due to the caller ID.  I noticed in the From field in your SIP header, the call is coming from 134457300 which is not a valid NANP number.  Try adding a caller ID mask to your DN configuration in CUCM and see if the call will complete properly after that.

0 Helpful

chet911
Level 1
Level 1

‎08-19-2020 08:24 AM

Your ITSP is most likely requiring authentication for calls. You'll need to configure digest authentication...

 

Here's the section from another post that explains is perfectly..

 

https://community.cisco.com/t5/collaboration-voice-and-video/handle-cube-registration-authentication-like-a-boss/ba-p/3660492 

CUBE Authentication


As opposed to registration, authentication is actually a method that ITSP uses to verify your identity.
Essentially, it uses authentication to decide whether we are allowed to make this call.
The role of authentication, from ITSP's point of view, is to allow you to make outgoing calls. Without it, every call attempt would be accepted and that's, well.. unacceptable!

 

In most cases, authentication should be pretty straight forward, if you pay attention to details that is (clue: skip to the troubleshooting section if you can't bear the suspense)

Parameters required:

  • Username
  • Password
  • Realm (domain)

Command syntax:

sip-ua
 authentication username username password [0/7] password realm realm

For example:

  • Username: ucpros
  • Password: 123456
  • Realm: ucpros.net

 

sip-ua
  authentication username ucpros password 0 123456 realm ucpros.net

 

0 Helpful

ArnoldKern
Level 1
Level 1
In response to chet911

‎08-20-2020 12:27 AM

I have done the configuration of SIP-UA despite one I have under voice-class sip tenant, but it didn't work. 

0 Helpful

davisjaron
Level 1
Level 1
In response to ArnoldKern

‎08-20-2020 06:28 AM - edited ‎08-20-2020 06:28 AM

If you don't mind, please share the following:

- output of show run

- output of show sip-ua register status

- outbound called number

 

Cheers

 

0 Helpful

ArnoldKern
Level 1
Level 1

‎08-19-2020 08:59 AM

@davisjaron 

Hi and thanks for the prompt answer. The CUBE and ITSP is in EU and therefore NANP is not an option here. Tee CUBE is registered successfully with ITSP. Incoming Calls are working. Only outbound calls are not functioning.

 

In my understanding in return to 401 Unauthorized CUBE should send register, but it never happened. Could it be because of the tag added in TO field?

0 Helpful

davisjaron
Level 1
Level 1
In response to ArnoldKern

‎08-19-2020 09:32 AM

Not a problem.  As was previously stated, it sounds like your ITSP requires credentials.  There are two sets of commands (usually they are the same credentials, though).  Under your SIP-UA configuration, you probably already have the authentication command.  Put in the exact same command, but using the word credentials instead of authentication.

 

sip-ua
authentication username [USERNAME] password [PASSWORD] realm [SIP REGISTRAR URL ADDRESS]
// used to register to SIP registrar
credentials username [USERNAME] password [PASSWORD] realm [SIP REGISTRAR URL ADDRESS]
// used to authenticate when sending calls
registrar 1 dns:[SIP REGISTRAR SIP REGISTRATION ADDRESS]
end

Customers Also Viewed These Support Documents