I rarely integrate these with Kamailio and am having some "resistance" in assisting. I was wondering if anyone would be willing to share any configuration recommendations for Mitel when using Kamailio as a SIP trunk (outbound/inbound).
Sincerely,
Fred Posner The Palner Group, Inc. http://www.palner.com (web) +1-503-914-0999 (direct)
Are there any specific issues you're encountering?
-- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Sent from my BlackBerry. Original Message From: Fred Posner Sent: Tuesday, August 18, 2015 09:22 To: sr-users@lists.sip-router.org Reply To: Kamailio (SER) - Users Mailing List Subject: [SR-Users] Mitel 5000 and 3000
I rarely integrate these with Kamailio and am having some "resistance" in assisting. I was wondering if anyone would be willing to share any configuration recommendations for Mitel when using Kamailio as a SIP trunk (outbound/inbound).
Sincerely,
Fred Posner The Palner Group, Inc. http://www.palner.com (web) +1-503-914-0999 (direct)
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 08/18/2015 09:23 AM, Alex Balashov wrote:
Are there any specific issues you're encountering?
Mostly hold issues where they try to speak directly with the media server vs the sip server; as well as general audio issues in/out.
Most of these seem to be acl related with a set-up issue on the Mitel. I don't work with Mitel enough to discuss in "Mitel speak" what to change. Apparently RTP ports is a different language to the people I am working with. =)
--fred
On 18/08/15 15:38, Fred Posner wrote:
On 08/18/2015 09:23 AM, Alex Balashov wrote:
Are there any specific issues you're encountering?
Mostly hold issues where they try to speak directly with the media server vs the sip server; as well as general audio issues in/out.
Most of these seem to be acl related with a set-up issue on the Mitel. I don't work with Mitel enough to discuss in "Mitel speak" what to change. Apparently RTP ports is a different language to the people I am working with. =)
Really long time since I used mitel, so I can't remember a thing from its configuration, probably they were old models anyhow, but they used to work ok with pretty much default options.
By "they try to speak directly with the media server vs the sip server" -- do you mean they ignore Record-Route headers added by the sip server?
Cheers, Daniel
On 08/20/2015 04:10 AM, Daniel-Constantin Mierla wrote:
By "they try to speak directly with the media server vs the sip server" -- do you mean they ignore Record-Route headers added by the sip server?
Cheers, Daniel
Yes, that would be a much better way of expressing the issue.
Without topology hiding, the Mitel will ignore Record-Route headers. If using topology hiding, they will send an in-dialog invite to the sdp c= address...
Can hack around it by using both topology hiding and rtpproxy but would rather see if I could get the Mitel to behave in a more respectful manner.
I've also thrown in either FreeSWITCH or Asterisk as a media server for those end-points to just "handle" it; which may end up being a decent solution for the trouble-making end-points.
--fred
On 20/08/15 14:26, Fred Posner wrote:
On 08/20/2015 08:25 AM, Fred Posner wrote:
[SNIP]
Without topology hiding, the Mitel will ignore Record-Route headers. If using topology hiding, they will send an in-dialog invite to the sdp c= address...
EDIT: on the o= information... I need more sleep. =)
If you use RTPProxy (RTPEngine) and flag 'o' in rtpproxy_manage(), then the IP in o= line is changed to the ip of the rtp relay application.
I think that is in default config file, as some UA don't like different IP in o= and c= lines.
Cheers, Daniel
Fred,
Throwing in B2BUAs is a common recipe for interop problems; one side is liberal in what it accepts, the other conservative in what it emits. In theory.
For lightweight, signalling-only duty, allow me to suggest SEMS + its 'sbc' module, though. It gives you a lot of low-level control to solve these kinds of interop problems, even if not quite as much as something programmable like Kamailio, and it's a lot less opaque and bureaucratic than Asterisk or Freeswitch. Email me offline if you want some sample configs, as the community documentation is a little light.
-- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Sent from my BlackBerry.
On 08/20/2015 08:34 AM, Alex Balashov wrote:
Fred,
Throwing in B2BUAs is a common recipe for interop problems; one side is liberal in what it accepts, the other conservative in what it emits. In theory.
For lightweight, signalling-only duty, allow me to suggest SEMS + its 'sbc' module, though. It gives you a lot of low-level control to solve these kinds of interop problems, even if not quite as much as something programmable like Kamailio, and it's a lot less opaque and bureaucratic than Asterisk or Freeswitch. Email me offline if you want some sample configs, as the community documentation is a little light.
-- Alex Balashov
I've been meaning to "test" SEMS for a while... This may just push me to it...
Thanks, and I'll get with you offline.
--fred
-
Alex Balashov -
Daniel-Constantin Mierla -
Fred Posner