SIP trunk rejecting anonymous callers

[StardataMitel]

We have a 3300 MCD v4.1 with SIP trunks that work fine ordinarily but when a caller blocks their ID the calls are rejected by the controller.

I've done some traces along with the SIP provider and we've noticed there is a 404 error sent by the system after the invite packet from the provider when the caller is anonymous. I've included some of the SIP trace from the system below if anyone is able to assist deciphering why it might do this.

Thanks...


2010-11-03 13:40:49 STS->Network SSP Level = 3 Unique ID = 0
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 125.213.160.83:5060;branch=z9hG4bK37dd5a0534cd0d9c2-a1159-0
From: "Anonymous" <sip:anonymous@sip20.mynetfone.com.au>;tag=452a65b-co6598-INS003
To: <sip:07xxxxxxxx@10.10.2.2:5060>;tag=0_3468154944-9xxxxxxx
Call-ID: e80-48c-103201034050-img-01-mas-2-125.213.168.3
CSeq: 659801 INVITE
Content-Length: 0

2010-11-03 13:40:49 App -> SSP SSP Level = 3 Unique ID = 0

Event Type : ClientErrResp
Call Object Id : 54
Session Id : 0x10b35388, Application ID : 5, Unique ID : 0
Request Type : 19
Reason Cause: 0
Reason Phrase :
Response Code : 404
Warning Code : 0 Warning Text :
Authentication Indicator : UndefinedTypeSecAgree Indicator : SecAgreeNoneSecurity Indicator : SecurityNone100rel Indicator : 100relNone
Min-Expires: 0Count: 0

2010-11-03 13:40:49 STS->Network SSP Level = 3 Unique ID = 0
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 125.213.160.83:5060;branch=z9hG4bK37dd5a0534cd0d9c2-a1159-0
From: "Anonymous" <sip:anonymous@sip20.mynetfone.com.au>;tag=452a65b-co6598-INS003
To: <sip:07xxxxxxxx@10.10.2.2:5060>;tag=0_3468154944-9xxxxxxx
Call-ID: e80-48c-103201034050-img-01-mas-2-125.213.168.3
CSeq: 659801 INVITE
Contact: <sip:10.10.2.2>
Content-Length: 0


2010-11-03 13:40:50 Network->STS SSP Level = 3 Unique ID = 0
ACK sip:07xxxxxxxx@10.10.2.2:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 125.213.160.83:5060;branch=z9hG4bK37dd5a0534cd0d9c2-a1159-0
To: <sip:07xxxxxxxx@10.10.2.2:5060>;tag=0_3468154944-9xxxxxxx
From: "Anonymous"<sip:anonymous@sip20.mynetfone.com.au>;tag=452a65b-co6598-INS003
Call-ID: e80-48c-103201034050-img-01-mas-2-125.213.168.3
CSeq: 659801 ACK
Content-Length: 0

 

[okcid]

Had the same issue,i.e. CLI blocked calls were dropped, this was solved by entering the incoming DID number correctly on the "SIP Peer Profile Assignment by Incoming DID form ", assigning it to a peer profile.

( Before, the Wireshark trace showed a 404 error code rejection code from the Mitel..s/w 9 and MCD4 )