Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mitel 5000 SIP trunks 6.0 SP4

Status
Not open for further replies.
yankblan

yankblan

Vendor
Jun 17, 2010
831
CA
Couldn't make it work on 5.0, 5.1 and now 6.0 with SP4

SIP provider works flawlessly on BCM, IP Office, SIP clients. I can only make calls from the Mitel, not receive any.

I have SIP between IP Office and Mitel 5000, problem is reversed; can receive not make.

Anyone has good experience with SIP and Mitel 5000? It doesn't look like a good combo so far...

 
Sort by date Sort by votes
Relatively new to the 5000 but I can at least verify that it is possible.

Our office has been running on SIP trunking for quite some time now without any issues.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Upvote 0 Downvote
Different SIP providers are configured completely differently in some cases. But we use SIP from different providers on various releases without issue (except the occasional trunk drop caused by the router), only exception being the first 6 release which caused total failure but that was fixed with a patch. And we also have an IPO linked to the 5000 again without issue and can do desk to desk both way with name/ number passing and breakout from the IP Office etc :)

 
Upvote 0 Downvote
Yeah, I got the IPO <=> 5000 working again; since they are labs the config was taken out and couldn't find the appropriate backups to get it to work again; plus IPO was upgraded to 9.0 in the meantime. Started from scratch.

Anyhow, now trying to get it to work with provider, haven't had any luck so far in many, many (too many) hours of testing.

 
Upvote 0 Downvote
I took some screenshots and edited for privacy but here is one working example:

Screenshots


**********************************************
What's most important is that you realise ... There is no spoon.
 
Upvote 0 Downvote
Thanks kwbMitel,

Still no go. I can dial out, but can't receive any calls. I have tried with single destinations, routing tables, nothing works. Without a way to monitor what is going on, I have no idea where it stops; at the router? the Mitel?

I put in the bare minimum to make it work, and added the settings in your screen shots, it had no impact on outgoing (so that's good), but also made no difference on incoming calls.

Not fun

ACSS-SME

 
Upvote 0 Downvote
Inbound issues are probably due to the digits received not having a matching termination point.

This is done via the trunk routing tables.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Upvote 0 Downvote
That's what I did. Put in in descending order the DID, then E and finally "." (I think, whatever the wild card for no digits received). Still no results.

I'll try to see if my provider can help me with a trace.

ACSS-SME

 
Upvote 0 Downvote
Sure sounds like your close. Good luck

**********************************************
What's most important is that you realise ... There is no spoon.
 
Upvote 0 Downvote
can you not get a wire shark traces ?

If its not broke tweak it..
 
Upvote 0 Downvote
BTW the wildcard is "+" in the call routing table
 
Upvote 0 Downvote
yankblan, reviewing the thread, you never mention the name of the SIP service provider.
In house we have SIP trunks between the IPO and 5000, MCD and 5000 work just fine.
Next, IPO and the MCD when time permits.
 
Upvote 0 Downvote
I use the Diagnostics Feature codes to enable the SIP output of Headers or Full output, then I check the SIP logs from the 5000's web interface, or through the System Admin and Diagnostics Tool.
I would place an inbound call, then look at some logs, to see if you even see this call arrive at the 5000.

With no logging, you run the risk of just taking guesses at what is wrong.
 
Upvote 0 Downvote
I did, and this is what it gave me; not very helpful IMO:

v=0
o=UserA 3111945738 2810945690 IN IP4 0.0.0.0
s=Session SDP
c=IN IP4 0.0.0.0
t=0 0
m=audio 8000 RTP/AVP 0 18
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
-01:232- >
-01:232- > -01:224- 16:41 11-29 *** SIP TX [''-'92003']: OPTIONS sip:montreal.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.60.75:5060;branch=z9hG4bK2987806275-915
Max-Forwards: 70
Allow: NOTIFY,REGISTER,REFER,SUBSCRIBE,INVITE,ACK,OPTIONS,CANCEL,BYE
User-Agent: Mitel-5000-ICP-6.0.9.67
P-Asserted-Identity: <sip:149760_mtl@192.168.60.75>
From: <sip:149760_mtl@192.168.60.75:5060>;tag=Mitel-5000_2987807005-915
To: sip:montreal.voip.ms:5060
Call-ID: 2987803275-915
CSeq: 1 OPTIONS
Contact: <sip:149760_mtl@192.168.60.75:5060>
Content-Length: 0

-01:232- >
-01:232- > -01:225- 16:41 11-29 *** SIP RX [''-'92003']: SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.60.75:5060;branch=z9hG4bK2987806275-915;received=205.237.45.113;rport=42628
From: <sip:149760_mtl@192.168.60.75:5060>;tag=Mitel-5000_2987807005-915
To: sip:montreal.voip.ms:5060;tag=as4ac02088
Call-ID: 2987803275-915
CSeq: 1 OPTIONS
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:67.205.74.184:5060>
Accept: application/sdp
Content-Length: 0

-01:232- >
-01:232- > -01:226- 16:42 11-29 *** SIP TX [''-'92002']: OPTIONS sip:192.168.60.70:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.60.75:5060;branch=z9hG4bK3017704453-915
Max-Forwards: 70
Allow: NOTIFY,REGISTER,REFER,SUBSCRIBE,INVITE,ACK,OPTIONS,CANCEL,BYE
User-Agent: Mitel-5000-ICP-6.0.9.67
From: <sip:192.168.60.75:5060>;tag=Mitel-5000_3017705140-915
To: sip:192.168.60.70:5060
Call-ID: 3017702639-915
CSeq: 1 OPTIONS
Contact: <sip:192.168.60.75:5060>
Content-Length: 0

-01:232- >
-01:232- > -01:227- 16:42 11-29 *** SIP RX [''-'92002']: SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.60.75:5060;branch=z9hG4bK3017704453-915
From: <sip:192.168.60.75:5060>;tag=Mitel-5000_3017705140-915
Call-ID: 3017702639-915
CSeq: 1 OPTIONS
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,UPDATE
Supported: timer
Server: IP Office 9.0.0.0 build 829
To: <sip:192.168.60.70:5060>;tag=3d374b34e63ba269
Content-Type: application/sdp
Content-Length: 184

v=0
o=UserA 2416200034 2356709533 IN IP4 0.0.0.0
s=Session SDP
c=IN IP4 0.0.0.0
t=0 0
m=audio 8000 RTP/AVP 0 18
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
-01:232- >
-01:232- > -01:228- 16:42 11-29 M3501 INF EG CP CP System Monitor Two Way Socket Thread Started From IP Address 192.168.60.117
-01:232- > -01:229- 16:42 11-29 *** SIP TX [''-'92003']: OPTIONS sip:montreal.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.60.75:5060;branch=z9hG4bK3047805749-915
Max-Forwards: 70
Allow: NOTIFY,REGISTER,REFER,SUBSCRIBE,INVITE,ACK,OPTIONS,CANCEL,BYE
User-Agent: Mitel-5000-ICP-6.0.9.67
P-Asserted-Identity: <sip:149760_mtl@192.168.60.75>
From: <sip:149760_mtl@192.168.60.75:5060>;tag=Mitel-5000_3047806487-915
To: sip:montreal.voip.ms:5060
Call-ID: 3047802801-915
CSeq: 1 OPTIONS
Contact: <sip:149760_mtl@192.168.60.75:5060>
Content-Length: 0

-01:232- >
-01:232- > -01:230- 16:42 11-29 *** SIP RX [''-'92003']: SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.60.75:5060;branch=z9hG4bK3047805749-915;received=205.237.45.113;rport=42628
From: <sip:149760_mtl@192.168.60.75:5060>;tag=Mitel-5000_3047806487-915
To: sip:montreal.voip.ms:5060;tag=as0600602a
Call-ID: 3047802801-915
CSeq: 1 OPTIONS
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:67.205.74.184:5060>
Accept: application/sdp
Content-Length: 0

ACSS-SME

 
Upvote 0 Downvote
Does the SIP Provider not supply config notes, is the 5000 even on their supported list?

In the the UK when we first started with SIP we used to configure the incoming numbers in the CRT as 01915000000, this then changed to +441915000000 for some reason, i'm guessing a change of platform at the providers end.

Have you tried your DDI in international format??

Other than that I would be chasing the Provider to help you out!

 
Upvote 0 Downvote
I dont see any call setup on that SIP output just option requests for keep alive you need to check your firewall or Nat from what you have shown it not the mitel causing the problem

If its not broke tweak it..
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

ctamir
  • Locked
  • Question
mitel 6920 sip
Replies
1
Views
719
HAPE67
H
kokolino23
  • Locked
  • Question
Virgin Media SIP trunks through MBG
Replies
2
Views
316
kokolino23
kokolino23
ctamir
  • Locked
  • Question
sip frimware for mitel 6920
Replies
1
Views
590
sarond
sarond
kokolino23
  • Locked
  • Question
Virgin Media SIP trunks through MBG
Replies
13
Views
1K
kokolino23
kokolino23
t3rm3y
  • Locked
  • Question
Migrating mitel asu to a grandstream sip 1
Replies
5
Views
1K
t3rm3y
t3rm3y

Part and Inventory Search

Sponsor

Back
Top