Sip trunk registration problem to an itsp

[antonio.dinapoli]

Hi,

I am trying to register a CUBE to an itsp without success.

I tried several configurations and I've read many community posts about this argument.

I have a Cisco router with IOS-XE Version 16.09.05.

I've also activated some debugs.

I notice this message from logs.

I don't know if it could be useful for troubleshooting.

Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP MYCUBEIP:5060;branch=z9hG4bK23971845
From: <sip:USERNAME@REALM@IP-PBX-ITSP>;tag=53C39B2-742
To: <sip:>;tag=aprqngfrt-v8c9h600000c0
Call-ID: 387410F-FFFFFFFF800511EB-FFFFFFFFAD20836F-FFFFFFFFBE36C364
Timestamp: 1615291724
CSeq: 6 REGISTER

Could anyone help me?

Thanks

Antonio

[TONY SMITH]

If you name the ITSP then it's possible someone has direct experience with them.  However I've found very little common ground between different ITSPs, what works for one will not necessarily work for another.  And unfortunately 400 is a very generic error more or less just meaning "something" is wrong with the request.

If you can post up the documentation from the provider, and a debug of your registration request and their response, we may be able to see what's wrong.  

[antonio.dinapoli]

Hi,

the provider is O2 Czech Republic.

Could you suggest any debug command to analyze registration phase?

thanks

[TONY SMITH]

We want to see SIP messages, so the basic debug is "debug ccsip messages". 

Some versions or platforms also need "debug ccsip non-call", otherwise they won't show the registration messages

Also give the command "term mon" so that logging messages appear on your screen.

[antonio.dinapoli]

Hi,

I activate the debus as you wrote me.

Here the logs.

You can notice that there are some messages between the two CUCM servers (IP is masked with the words "IP_CUCM1" and "IP_CUCM2") and my router (IP is masked with the word "IP_MYCUBE"): these SIP sessions are based on TCP.

SIP messages between my router and itsp sip server (IP is masked with the word "IP_ITSP") are based  on UDP.

Of course also username and realm are masked with that words.

I notice different messages with the ITSP, especially in the TO section but also in the FROM section.

Mar 10 12:16:13.267: //162/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:USERNAME@REALM@IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:13 GMT
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615374973
CSeq: 7 REGISTER
Contact: <sip:USERNAME@REALM@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0

Mar 10 12:16:13.271: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:>;tag=aprqngfrt-dia4ld10000e0
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
Timestamp: 1615374973
CSeq: 7 REGISTER

Mar 10 12:16:15.539: //163/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_CUCM1:5060 SIP/2.0
Via: SIP/2.0/TCP IP_MYCUBE:5060;branch=z9hG4bK781177
From: <sip:IP_MYCUBE>;tag=12E1E4-592
To: <sip:IP_CUCM1>
Date: Wed, 10 Mar 2021 11:16:15 GMT
Call-ID: DD0D3FD1-80C811EB-809FB434-6BA0A90A@IP_MYCUBE
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060;transport=tcp>
Content-Length: 0

Mar 10 12:16:15.540: //164/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_CUCM2:5060 SIP/2.0
Via: SIP/2.0/TCP IP_MYCUBE:5060;branch=z9hG4bK79140
From: <sip:IP_MYCUBE>;tag=12E1E5-CF6
To: <sip:IP_CUCM2>
Date: Wed, 10 Mar 2021 11:16:15 GMT
Call-ID: DD0D668F-80C811EB-80A0B434-6BA0A90A@IP_MYCUBE
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060;transport=tcp>
Content-Length: 0

Mar 10 12:16:15.578: //163/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP IP_MYCUBE:5060;branch=z9hG4bK781177
From: <sip:IP_MYCUBE>;tag=12E1E4-592
To: <sip:IP_CUCM1>;tag=215231523
Date: Wed, 10 Mar 2021 11:16:15 GMT
Call-ID: DD0D3FD1-80C811EB-809FB434-6BA0A90A@IP_MYCUBE
Server: Cisco-CUCM11.5
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0

Mar 10 12:16:15.579: //164/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP IP_MYCUBE:5060;branch=z9hG4bK79140
From: <sip:IP_MYCUBE>;tag=12E1E5-CF6
To: <sip:IP_CUCM2>;tag=143645191
Date: Wed, 10 Mar 2021 11:16:15 GMT
Call-ID: DD0D668F-80C811EB-80A0B434-6BA0A90A@IP_MYCUBE
Server: Cisco-CUCM11.5
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0

Mar 10 12:16:17.267: //162/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:USERNAME@REALM@IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:17 GMT
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615374977
CSeq: 7 REGISTER
Contact: <sip:USERNAME@REALM@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0

Mar 10 12:16:17.270: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:>;tag=aprqngfrt-dia4ld10000e0
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
Timestamp: 1615374977
CSeq: 7 REGISTER

Mar 10 12:16:21.267: //162/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:USERNAME@REALM@IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:21 GMT
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615374981
CSeq: 7 REGISTER
Contact: <sip:USERNAME@REALM@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0

Mar 10 12:16:21.271: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:>;tag=aprqngfrt-dia4ld10000e0
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
Timestamp: 1615374981
CSeq: 7 REGISTER

Mar 10 12:16:25.267: //162/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:USERNAME@REALM@IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:25 GMT
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615374985
CSeq: 7 REGISTER
Contact: <sip:USERNAME@REALM@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0

Mar 10 12:16:25.273: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:>;tag=aprqngfrt-dia4ld10000e0
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
Timestamp: 1615374985
CSeq: 7 REGISTER

Mar 10 12:16:29.068: //165/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK7A508
From: <sip:IP_MYCUBE>;tag=1316BD-1995
To: <sip:IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:29 GMT
Call-ID: E51D9D02-80C811EB-80A1B434-6BA0A90A@IP_MYCUBE
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060>
Content-Length: 0

Mar 10 12:16:29.073: //165/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK7A508
From: <sip:REALM>;tag=1316BD-1995
To: <sip:IP_ITSP>;tag=aprqse5ef6ech1s83-61vkdm10000a6
Call-ID: E51D9D02-80C811EB-80A1B434-6BA0A90A@IP_MYCUBE
CSeq: 101 OPTIONS

Mar 10 12:16:29.267: //162/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:USERNAME@REALM@IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:29 GMT
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615374989
CSeq: 7 REGISTER
Contact: <sip:USERNAME@REALM@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0

Mar 10 12:16:29.272: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:>;tag=aprqngfrt-dia4ld10000e0
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
Timestamp: 1615374989
CSeq: 7 REGISTER

Mar 10 12:16:33.267: //162/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:USERNAME@REALM@IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:33 GMT
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615374993
CSeq: 7 REGISTER
Contact: <sip:USERNAME@REALM@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0

Mar 10 12:16:33.272: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:>;tag=aprqngfrt-dia4ld10000e0
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
Timestamp: 1615374993
CSeq: 7 REGISTER

Mar 10 12:16:33.643: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:IP_MYCUBE:5060 SIP/2.0
Via: SIP/2.0/TCP IP_CUCM1:5060;branch=z9hG4bK80eaa71757af0d
From: <sip:IP_CUCM1>;tag=1012626282
To: <sip:IP_MYCUBE>
Date: Wed, 10 Mar 2021 11:16:33 GMT
Call-ID: 10a78400-481aa91-1bdc46-100310ac@IP_CUCM1
User-Agent: Cisco-CUCM11.5
CSeq: 101 OPTIONS
Contact: <sip:IP_CUCM1:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0

Mar 10 12:16:33.645: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP IP_CUCM1:5060;branch=z9hG4bK80eaa71757af0d
From: <sip:IP_CUCM1>;tag=1012626282
To: <sip:IP_MYCUBE>;tag=13289D-4C4

Date: Wed, 10 Mar 2021 11:16:33 GMT
Call-ID: 10a78400-481aa91-1bdc46-100310ac@IP_CUCM1
Server: Cisco-SIPGateway/IOS-16.9.5
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 380

v=0
o=CiscoSystemsSIP-GW-UserAgent 766 7662 IN IP4 IP_MYCUBE
s=SIP Call
c=IN IP4 IP_MYCUBE
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3
c=IN IP4 IP_MYCUBE
m=image 0 udptl t38
c=IN IP4 IP_MYCUBE
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

Mar 10 12:16:37.268: //162/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:USERNAME@REALM@IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:37 GMT
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615374997
CSeq: 7 REGISTER
Contact: <sip:USERNAME@REALM@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0

Mar 10 12:16:37.272: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:>;tag=aprqngfrt-dia4ld10000e0
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
Timestamp: 1615374997
CSeq: 7 REGISTER

Mar 10 12:16:41.268: //162/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:USERNAME@REALM@IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:41 GMT
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615375001
CSeq: 7 REGISTER
Contact: <sip:USERNAME@REALM@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0

Mar 10 12:16:41.273: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:>;tag=aprqngfrt-dia4ld10000e0
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
Timestamp: 1615375001
CSeq: 7 REGISTER

Mar 10 12:16:45.579: //167/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_CUCM1:5060 SIP/2.0
Via: SIP/2.0/TCP IP_MYCUBE:5060;branch=z9hG4bK7B1006
From: <sip:IP_MYCUBE>;tag=13573D-1F80
To: <sip:IP_CUCM1>

Date: Wed, 10 Mar 2021 11:16:45 GMT
Call-ID: EEF52450-80C811EB-80A3B434-6BA0A90A@IP_MYCUBE
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060;transport=tcp>
Content-Length: 0

Mar 10 12:16:45.580: //168/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_CUCM2:5060 SIP/2.0
Via: SIP/2.0/TCP IP_MYCUBE:5060;branch=z9hG4bK7C2482
From: <sip:IP_MYCUBE>;tag=13573E-168E
To: <sip:IP_CUCM2>
Date: Wed, 10 Mar 2021 11:16:45 GMT
Call-ID: EEF54B0D-80C811EB-80A4B434-6BA0A90A@IP_MYCUBE
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060;transport=tcp>
Content-Length: 0

Mar 10 12:16:45.618: //167/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP IP_MYCUBE:5060;branch=z9hG4bK7B1006
From: <sip:IP_MYCUBE>;tag=13573D-1F80
To: <sip:IP_CUCM1>;tag=18286805
Date: Wed, 10 Mar 2021 11:16:45 GMT
Call-ID: EEF52450-80C811EB-80A3B434-6BA0A90A@IP_MYCUBE
Server: Cisco-CUCM11.5
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0

Mar 10 12:16:45.619: //168/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/TCP IP_MYCUBE:5060;branch=z9hG4bK7C2482
From: <sip:IP_MYCUBE>;tag=13573E-168E
To: <sip:IP_CUCM2>;tag=643539026
Date: Wed, 10 Mar 2021 11:16:45 GMT

Call-ID: EEF54B0D-80C811EB-80A4B434-6BA0A90A@IP_MYCUBE
Server: Cisco-CUCM11.5
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0

Mar 10 12:16:55.621: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
OPTIONS sip:IP_MYCUBE:5060 SIP/2.0
Via: SIP/2.0/TCP IP_CUCM2:5060;branch=z9hG4bK1c0ace3236cb71
From: <sip:IP_CUCM2>;tag=792629293
To: <sip:IP_MYCUBE>
Date: Wed, 10 Mar 2021 11:16:55 GMT
Call-ID: 1dc47300-481aaa7-12d4d6-110310ac@IP_CUCM2
User-Agent: Cisco-CUCM11.5
CSeq: 101 OPTIONS
Contact: <sip:IP_CUCM2:5060;transport=tcp>
Max-Forwards: 0
Content-Length: 0

Mar 10 12:16:55.623: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP IP_CUCM2:5060;branch=z9hG4bK1c0ace3236cb71
From: <sip:IP_CUCM2>;tag=792629293
To: <sip:IP_MYCUBE>;tag=137E77-7A8
Date: Wed, 10 Mar 2021 11:16:55 GMT
Call-ID: 1dc47300-481aaa7-12d4d6-110310ac@IP_CUCM2
Server: Cisco-SIPGateway/IOS-16.9.5
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Accept: application/sdp
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Content-Type: application/sdp
Content-Length: 380

v=0
o=CiscoSystemsSIP-GW-UserAgent 186 5151 IN IP4 IP_MYCUBE
s=SIP Call
c=IN IP4 IP_MYCUBE
t=0 0
m=audio 0 RTP/AVP 18 0 8 9 4 2 15 3

c=IN IP4 IP_MYCUBE
m=image 0 udptl t38
c=IN IP4 IP_MYCUBE
a=T38FaxVersion:0
a=T38MaxBitRate:9600
a=T38FaxRateManagement:transferredTCF
a=T38FaxMaxBuffer:200
a=T38FaxMaxDatagram:320
a=T38FaxUdpEC:t38UDPRedundancy

Mar 10 12:16:59.073: //170/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK7D1185
From: <sip:IP_MYCUBE>;tag=138BF2-2D1
To: <sip:IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:59 GMT
Call-ID: F7002AD6-80C811EB-80A6B434-6BA0A90A@IP_MYCUBE
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060>
Content-Length: 0

Mar 10 12:16:59.078: //170/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK7D1185
From: <sip:REALM>;tag=138BF2-2D1
To: <sip:IP_ITSP>;tag=aprqse5ef6ech1s83-p1hrck00000a6
Call-ID: F7002AD6-80C811EB-80A6B434-6BA0A90A@IP_MYCUBE
CSeq: 101 OPTIONS

[TONY SMITH]

The Options requests, and their "200 OK" responses are a form of keepalive, normally these are configured on the CUBE dial peers - if the keepalives fail then the dial peer goes out of service.  So from the trace I can see the ITSP replying to your Options polls which suggests the IP addressing is probably OK ..

Mar 10 12:16:59.073: //170/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK7D1185
From: <sip:IP_MYCUBE>;tag=138BF2-2D1
To: <sip:IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:59 GMT
Call-ID: F7002AD6-80C811EB-80A6B434-6BA0A90A@IP_MYCUBE
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060>
Content-Length: 0

Mar 10 12:16:59.078: //170/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK7D1185
From: <sip:REALM>;tag=138BF2-2D1
To: <sip:IP_ITSP>;tag=aprqse5ef6ech1s83-p1hrck00000a6
Call-ID: F7002AD6-80C811EB-80A6B434-6BA0A90A@IP_MYCUBE
CSeq: 101 OPTIONS

Obviously they're not happy with the format or contents of your registration ..

Mar 10 12:16:41.268: //162/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:USERNAME@REALM@IP_ITSP>
Date: Wed, 10 Mar 2021 11:16:41 GMT
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615375001
CSeq: 7 REGISTER
Contact: <sip:USERNAME@REALM@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0


Mar 10 12:16:41.273: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 400 Invalid From
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK77F69
From: <sip:USERNAME@REALM@IP_ITSP>;tag=12CB58-41D
To: <sip:>;tag=aprqngfrt-dia4ld10000e0
Call-ID: 54F451B4-FFFFFFFF80C611EB-FFFFFFFF8002B434-6BA0A90A
Timestamp: 1615375001
CSeq: 7 REGISTER

In the absence of your configuration, or any info from O2 about how their service is configured, I can see some differences from what I'd expect.  In the register request I'd expect to see the URI in the form "REGISTER sip:REALM:5060", and both From and To in the form "To: <sip:USERNAME@REALM>"  Rather than "USERNAME@REALM@IP-ADDRESS"

It may or may not be significant that their error actually cites the From header in "SIP/2.0 400 Invalid From"

Can you share the info provided by O2, and also your "voice service" and "sip-ua" configuration?  Feel from to replace the sensitive information as long as it's clear what refers to what.

[antonio.dinapoli]

Hi,

thanks for your reply.

I have written some days ago to the ITSP about URI in the form of Register message but I am still waiting for the response.

These are my configurations and at last some O2 parameters.

***  VOICE SERVICE VOIP ***

voice service voip
ip address trusted list
   ipv4 IP_CUCM1
   ipv4 IP_CUCM2
   ipv4 IP_ITSP
dtmf-interworking rtp-nte
mode border-element license capacity 30
media disable-detailed-stats
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
sip
   bind control source-interface ID_INTF
   bind media source-interface ID_INTF
   early-offer forced
   pass-thru content sdp

Maybe I don't need the last two commands. I add these commands just for some tests.

*** SIP-UA ***
sip-ua
  credentials username USERNAME@REALM password PASSWORD realm REALM
  authentication username USERNAME@REALM password PASSWORD realm REALM
  retry invite 10
  retry response 4
  retry bye 1
  retry register 10
  timers trying 1000
  timers expires 360000
  timers connect 100
  timers buffer-invite 500
  registrar ipv4:IP_ITSP expires 3600
  sip-server ipv4:IP_ITSP

I add the "timers" commands to do some test but I don't know if they are right. I don't think that they are important now.

*** O2 main parameters**

Protocol: UDP

Port: 5060

DMTF: RFC 2833

Primary codec: g.729a p-time: 20ms

Secondary codec: g.711alaw

[TONY SMITH]

Try changing your credentials to ...

sip-ua
  credentials username USERNAME password PASSWORD realm REALM
  authentication username USERNAME password PASSWORD realm REALM

Regarding the timers, the one I normally tweak is "trying", that's the timeout from when an Invite is sent until 100 Trying is received.  I also reduce the number of retries.  This is only really important if you want some alternative action if the trunk fails.  For example the defaults (6 retries, 500ms timer) means it tries for over 30 seconds before giving up.

Assuming you have a SIP trunk to CUCM, you only need the last "allow-connections" line (sip to sip).

There are probably other tweaks, but let's get registration working first.

[antonio.dinapoli]

Hi,

thanks for this suggestion.

I configure the credentials as you have written.

It doesn't register but maybe the Register messages change: now I receive a USER UNKNOWN response.

Here the new register messages.

Mar 10 19:40:34.515: //3826/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB5D4D6
From: <sip:IP_MYCUBE>;tag=1A9AA84-1D2E
To: <sip:IP_ITSP>
Date: Wed, 10 Mar 2021 18:40:34 GMT
Call-ID: EF0A29C9-810611EB-8E73B434-6BA0A90A@IP_MYCUBE
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70

CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060>
Content-Length: 0

Mar 10 19:40:34.518: //3826/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB5D4D6
From: <sip:REALM>;tag=1A9AA84-1D2E
To: <sip:IP_ITSP>;tag=aprqse5ef6ech1s83-18rdhh10000a6
Call-ID: EF0A29C9-810611EB-8E73B434-6BA0A90A@IP_MYCUBE
CSeq: 101 OPTIONS

Mar 10 19:41:04.520: //3830/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB601A21
From: <sip:IP_MYCUBE>;tag=1AA1FB9-1351
To: <sip:IP_ITSP>
Date: Wed, 10 Mar 2021 18:41:04 GMT
Call-ID: EC9047-810711EB-8E77B434-6BA0A90A@IP_MYCUBE

User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060>
Content-Length: 0

Mar 10 19:41:04.524: //3830/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB601A21
From: <sip:REALM>;tag=1AA1FB9-1351
To: <sip:IP_ITSP>;tag=aprqse5ef6ech1s83-kveg0630000a6
Call-ID: EC9047-810711EB-8E77B434-6BA0A90A@IP_MYCUBE
CSeq: 101 OPTIONS

Mar 10 19:41:34.525: //3834/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB6323CF
From: <sip:IP_MYCUBE>;tag=1AA94EE-1B4F
To: <sip:IP_ITSP>
Date: Wed, 10 Mar 2021 18:41:34 GMT
Call-ID: 12CF1D83-810711EB-8E7BB434-6BA0A90A@IP_MYCUBE

User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060>
Content-Length: 0

Mar 10 19:41:34.531: //3834/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB6323CF
From: <sip:REALM>;tag=1AA94EE-1B4F
To: <sip:IP_ITSP>;tag=aprqse5ef6ech1s83-19vbl720000a6
Call-ID: 12CF1D83-810711EB-8E7BB434-6BA0A90A@IP_MYCUBE
CSeq: 101 OPTIONS

Mar 10 19:41:48.241: //3835/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB641ED0
From: <sip:USERNAME@IP_ITSP>;tag=1AACA82-13A1

To: <sip:USERNAME@IP_ITSP>
Date: Wed, 10 Mar 2021 18:41:48 GMT
Call-ID: 44594485-FFFFFFFF810611EB-FFFFFFFF8E4CB434-6BA0A90A
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
Timestamp: 1615401708
CSeq: 4 REGISTER
Contact: <sip:USERNAME@IP_MYCUBE:5060>
Expires: 3600
Supported: path
Content-Length: 0

Mar 10 19:41:48.340: //3835/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Forbidden - 6034 user unknown
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB641ED0
From: <sip:USERNAME@IP_ITSP>;tag=1AACA82-13A1
To: <sip:USERNAME@IP_ITSP>;tag=159853325
Call-ID: 44594485-FFFFFFFF810611EB-FFFFFFFF8E4CB434-6BA0A90A
Timestamp: 1615401708
CSeq: 4 REGISTER

Content-Length: 0

Mar 10 19:42:04.532: //3839/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:IP_ITSP:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB67D86
From: <sip:IP_MYCUBE>;tag=1AB0A25-17E4
To: <sip:IP_ITSP>
Date: Wed, 10 Mar 2021 18:42:04 GMT
Call-ID: 24B1AABF-810711EB-8E7FB434-6BA0A90A@IP_MYCUBE
User-Agent: Cisco-SIPGateway/IOS-16.9.5
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:IP_MYCUBE:5060>
Content-Length: 0

Mar 10 19:42:04.535: //3839/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB67D86
From: <sip:REALM>;tag=1AB0A25-17E4
To: <sip:IP_ITSP>;tag=aprqse5ef6ech1s83-vvjp4010000a6
Call-ID: 24B1AABF-810711EB-8E7FB434-6BA0A90A@IP_MYCUBE
CSeq: 101 OPTIONS

[TONY SMITH]

I would have expected those headers to be more like ..

REGISTER sip:REALM:5060 SIP/2.0
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bKB641ED0
From: <sip:USERNAME@REALM>;tag=1AACA82-13A1
To: <sip:USERNAME@REALM>

We might need to look further at your configuration, but meantime send that Register message and their response to the ITSP and ask them what's wrong with your request.

[antonio.dinapoli]

Hi,

the strange thing is that the messages that my CUBE sends to ITSP have the IP address of provider in FROM section.

This is the error that provider reports to me and the strange thing that I also notice and it is reported in the previous logs.

For example this is a typical debug log about a call originated in my site to sip trunk

SIP/2.0 100 Trying
Via: SIP/2.0/UDP IP_MYCUBE:5060;branch=z9hG4bK46F8F23
From: "IDPHONE" <sip:USERNAME@IP_ITSP>;tag=A82736E-1423
To: <sip:CALLEDNUMBER@IP_ITSP>
Call-ID: 83325EAC-826011EB-9BFAB434-6BA0A90A@IP_MYCUBE
CSeq: 101 INVITE
Timestamp: 1615550059
Content-Length: 0

In the from section there should be the IP address of CUBE and not the ip address of ITSP.

I don't understand why there is such information

thanks for your suggestion

antonio

[TONY SMITH]

In a response the To and From headers remain the same as the To and From of the initial request.  They're not indicating the sender or receiver of that particular message, but the sender and receiver of the call that's being attempted.  Can you show the Invite that this message was in response to?

Although until your trunk is registered it may be a bit pointless expecting calls to work.

[antonio.dinapoli]

Hi,

finally it works.

As also you have suggested, it was very important a feedback that the provider has given to me some days ago about some transformations regarding FROM and TO sections of SIP messages.

In fact, as we also have noticed, the standard SIP messages weren't incompatible each other.

The IPV4 address of ITSP SIP SERVER is reported as A.B.C.D

voice class sip-profiles 1
request ANY sip-header From modify "@A\.B\.C\.D>" "@ITSP_REALM>"
request ANY sip-header To modify "@A\.B\.C\.D>" "@ITSP_REALM>"

The sip profiles is then associated to sip section under voice service voip configuration.

The provider also has suggested this configuration for the sip-ua section.

sip-ua
credentials number NUMBER username USERNAME@REALM password PASSWORD realm REALM
no remote-party-id
retry invite 2
retry register 5
registrar ipv4:A.B.C.D expires 600 auth-realm REALM
connection-reuse
host-registrar

Thanks a lot for your support.