Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Domrac45

Pages: [1]
1
Hi, we're currently doing that for a 5000 + users. We're now at the point of fine tuning. Calls works fine, inside to outside, outside to inside (almost), but I have a very anoying thing happening to me and I have no clue what is the cause.

Here's my set-up resume: Mitel pbxs, Unify SBC, Teams office 365 infra. Got my trunk/SIP peer profile/ars route worked out, but when I was doing some testing we couldn't place call to certain cellphones providers.

In the Call routing tab of my SIP peer Profile, I setted the "Private SIP Trunk" to Yes. Since then, I can call everywhere without problem, but since the modification, I lost the ring back tone when we place a call from an device to my Teams extension. To fixed that, in the "Signaling and Header Manipulation", I changed "Require Reliable Provisional Responses on Outgoing Calls" to No and I got the ring back tone again BUT NOW instead of the extension number I see on the phone's acd screen "Private Ringing".

Look like it's a never ending series of I fixe something to create an other problem.

thanks

2
Ohhhhhh makes so much sense, I had unmatching number for the timers. I corrected it remotly, can wait for tomorrow morning.

3
here's my current configurations:

Call Routing and Administration Options
   Outbound Proxy Server      
   Replace System based with Device based In-Call Features      Yes
   Allow MWI Notifications without Subscription      No
   Enable Digit Collection In Busy Or Alerting State      No

Allow Device To Use Multiple Active M-Lines      Yes
Allow Using UPDATE For Early Media Renegotiation      Yes
AVP Only Device      Yes
Enable Mitel Proprietary SDP      Yes
Force sending SDP in initial Invite message      No
Ignore SDP Answers in Provisional Responses      No
Limit to one Offer/Answer per INVITE      No
Prevent SDP Renegotiation If Peer Initiated Hold      Yes
Prevent the Use of IP Address 0.0.0.0 in SDP Messages      Yes
Renegotiate SDP To Enforce Symmetric Codec      No
Repeat SDP Answer If Duplicate Offer Is Received      No
Send Answer only after renegotiation is complete      No
Suppress Use of SDP Inactive Media Streams      No

Allow Display Update      Yes
Disable Reliable Provisional Responses      No
Disable Use of User-Agent and Server Headers      No
Fail REFER To Keep Call Active On Mid-Call Feature      No
If TLS use 'sips:' Scheme      No
Multilingual Name Display      No
Override Auto-Answer Headers      No
Override Auto-Answer Headers With      
Remove Anonymous User      No
Require Reliable Provisional Responses on Outgoing Calls      No
Suppress Redirection Headers      No
Use P-Asserted Identity Header      Yes
Use user=phone      No

Registration Period Minimum      300
Session Timer      90
Session Timer: Local as Refresher      No
Subscription Period      3600
Subscription Period Minimum      300
Subscription Period Refresh (%)      80
Invite Ringing Response Timer      4

On the SIP module, I'v got green light, I Ping my PBX, able to make and receive calls for couple of minutes and it stops working. There's something somewhere been trying to figure it out for days...

4
SIP On Mitel / 5634 wireless call problems
« on: November 17, 2023, 10:14:40 AM »
Hi, just got promoted to the telephony department, pretty green with Mitel systems, a lot a experience in IT in general. I have a 5634 phone with either a no access error or occupied line. I double checked the configuration with Winpdm. I noticed a error VoIp/SIP parameter. Corrrect it, didn't change a thing. I found that the device type in the pbx profile was at 5624 IP phone. Change it, to Generic SIP phone, the no access error went away, but now when we try to make a phone call it says line occupied and if we tried to call the phone it says the same thing.

Any one as a clue?

Pages: [1]