07-27-2015 11:21 AM - edited 03-17-2019 03:46 AM
*Jul 27 17:26:14.090: %VOICE_IEC-3-GW: SIP: Internal Error (INVITE, invalid IE content): IEC=1.1.100.7.35.1 on callID -1
Having an issue where calls inbound from the provider are failing on the CUBE with the error above. This is new behavior that was not happening before. As far as I know there have been no changes on the CUBE and the Firewall guys are telling me they made no changes. Look at the logs below and let me know what you think. Thanks in advance.
(These IPs are modified for public posting)
The Providers signaling address is 1.1.1.1
My public outside address is 2.2.2.2
The public outside is NAT’ed to 3.3.3.3 (Gi0/0 on the CUBE)
The invite comes in from the provider via the firewall like this:
Received:
INVITE sip:01707245311@2.2.2.2;user=phone SIP/2.0
Max-Forwards: 69
Session-Expires: 3600;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:01707245311@1.1.1.1:5060;user=phone>
From: <sip:+14123787719@1.1.1.1>;tag=94gdrrh9r
P-Asserted-Identity: <sip:+14123787719@1.1.1.1;user=phone>
Call-ID: 14918063-3647002470-287476@MSX62.SipProvider.com
CSeq: 1 INVITE
Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK4829443535aaed05d29650dcdfdc2a15
Contact: <sip:+14123787719@1.1.1.1:5060>
Content-Type: application/sdp
Accept: application/sdp
Content-Length: 211
The CUBE logs this error:
*Jul 27 17:26:14.090: %VOICE_IEC-3-GW: SIP: Internal Error (INVITE, invalid IE content): IEC=1.1.100.7.35.1 on callID -1
Then the CUBE sends this:
Sent:
SIP/2.0 400 Bad Request - 'Invalid Host'
Via: SIP/2.0/UDP 1.1.1.1:5060;branch=z9hG4bK4829443535aaed05d29650dcdfdc2a15
From: <sip:+14123787719@1.1.1.1>;tag=94gdrrh9r
To: <sip:01707245311@1.1.1.1:5060;user=phone>;tag=237DAD70-1885
Date: Mon, 27 Jul 2015 16:08:43 GMT
Call-ID: 14918063-3647002470-287476@MSX62.SipProvider.com
CSeq: 1 INVITE
Allow-Events: telephone-event
Reason: Q.850;cause=100
Server: Cisco-SIPGateway/IOS-15.4.3.M1
Content-Length: 0
What I think (or what I thought) was that the Request-URI Host Part of 2.2.2.2. So I wrote this SIP Profile and applied it to the inbound dial peer. There was no change.
voice class sip-profiles 2
request INVITE sip-header SIP-Req-URI modify "(.*:)(.*@)(2.2.2.2)" "\1\23.3.3.3"
dial-peer voice 10 voip
description INCOMING PSTN dial peer
translation-profile incoming PSTN_INBOUND
session protocol sipv2
incoming called-number .
voice-class codec 1
voice-class sip early-offer forced
voice-class sip profiles 2
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte
07-27-2015 01:04 PM
Hi,
It could be some call are matching Dial-Peer 0 or a wrong dial-peer.
Could you please send the result of those command:
Debug voice ccapi inout
debug voice dialpeer inout
Regards
07-27-2015 01:23 PM
Just adding to what Leo has requested, if possible, could you please post the current config as well?
Regards
07-27-2015 07:26 PM
All, Thanks for the help. Turns out the issue was caused by the Firewall team messing with SIP Inspect.
Dennis, were right. I left the SDP out of what I had posted here.
07-27-2015 11:37 PM
thanks for letting us know what it was, and thx for the ratings
07-27-2015 04:10 PM
That error message is very generic:
INVITE with either invalid header contents, SDP, or VIA parameters was received.
I also noticed there is no SDP in the INVITE that you added in your original post, is this because your provider is using Delayed offer, or did you not past all the invite contents in?
cheers
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