Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: Ray B on May 10, 2010, 10:28:55 PM

Title: SIP Incoming call failure
Post by: Ray B on May 10, 2010, 10:28:55 PM

Incoming SIP calls from DN@anonymous.invalid fail.
Incoming SIP calls from anonymous@anonymous.invalid work fine.
The controller is running MCD 4 SP1, SIP carrier is Paetec Dynamic SIP.

Title: Re: SIP Incoming call failure
Post by: Mitel100 on May 11, 2010, 04:29:52 AM

Hi Ray B,

Can you paste your SIP Peer profile information?

Title: Re: SIP Incoming call failure
Post by: Ray B on May 11, 2010, 10:07:24 AM

I've masked the range of DID's and IP addresses for the privacy and security of the customer.




SIP Peer Profile Label   Network Element   Registration User Name   Address Type   Interconnect Restriction   Maximum Simultaneous Calls   Outbound Proxy Server   SMDR Tag   Trunk Service   Zone   Alternate Destination Domain Enabled   Alternate Destination Domain FQDN or IP Address   Enable Special Re-invite Collision Handling   Private SIP Trunk   Route Call Using To Header   Default CPN   CPN Restriction   Public Calling Party Number Passthrough   Use Diverting Party Number as Calling Party Number   User Name   Password   Confirm Password   Authentication Option for Incoming Calls   Allow Peer To Use Multiple Active M-Lines   Enable Mitel Proprietary SDP   Force sending SDP in initial Invite message   Force sending SDP in initial Invite - Early Answer   NAT Keepalive   Prevent the Use of IP Address 0.0.0.0 in SDP Messages   Renegotiate SDP To Enforce Symmetric Codec   Repeat SDP Answer If Duplicate Offer Is Received   RTP Packetization Rate Override   RTP Packetization Rate   Special handling of Offers in 2XX responses (INVITE)   Suppress Use of SDP Inactive Media Streams   Session Timer   Build Contact Using Request URI Address   Disable Reliable Provisional Responses   Enable sending '+' for E.164 numbers   Ignore Incoming Loose Routing Indication   Use P-Asserted Identity Header   Use P-Preferred Identity Header   Use Restricted Character Set For Authentication   Use To Address in From Header on Outgoing Calls
Paetech   b7d5f9c0-1dd1-11b2-872a-08000f38bb15   (NNN)NNN-NNNN-(NNN)NNN-NNNN IP Address: XXX.XXX.XXX.XXX   1   16      0   11   1   No      No   No   No   (NNN)NNN-NNNN   No   No   No            No Authentication   No   Yes   Yes   No   No   Yes   No   No   No   0   No   No   1800   No   Yes   No   No   No   No   No   No

Title: Re: SIP Incoming call failure
Post by: Chakara on May 12, 2010, 01:19:34 AM

Ray,

  Please don't take offence, but the way that post came out it takes a LOT of work to decipher.  Any chance you could clean it up a bit?

-Chak

Title: Re: SIP Incoming call failure
Post by: Ray B on May 13, 2010, 09:25:59 AM

The issue has been resolved, the problem didn't occur on the previous load (rel 9) On rel 10 (it seems) I needed to add the incoming DID range to the  SIP Peer Profile Assignment by Incoming DID.