Messages

1

Mitel MiVoice Business/MCD/3300 / Re: Basic SPA8000 configuration to connect to MiVB with SIP Trunking

« on: May 07, 2020, 09:25:45 AM »

Session Initiation Protocol (INVITE)
    Request-Line: INVITE sip:xxxxxxxxxx@x.x.x.xSIP/2.0
    Message Header
        Via: SIP/2.0/UDP x.x.x.x:5060;branch=z9hG4bK-c60f402a
        From: "1122" <sip:xxx@x.x.x.x>;tag=28b0ef2c58330edao1
        To: <sip:xxxxxxxxxx@x.x.x.x>
        Remote-Party-ID: "xxxx" <sip:xxxx@x.x.x.x>;screen=yes;party=calling
            [Expert Info (Note/Undecoded): Unrecognised SIP header (remote-party-id)]
                [Unrecognised SIP header (remote-party-id)]
                [Severity level: Note]
                [Group: Undecoded]
        Call-ID: 4b9a4b14-3ce32412@x.x.x.x
        [Generated Call-ID: 4b9a4b14-3ce32412@x.x.x.x]
        CSeq: 101 INVITE
            Sequence Number: 101
            Method: INVITE
        Max-Forwards: 70
        Contact: "xxxx" <sip:xxxx@x.x.x.x:5060>
        Expires: 240
        User-Agent: Linksys/SPA8000-6.1.12SR1
        Allow-Events: talk, hold, conference
        Content-Length: 444
        Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
        Supported: x-sipura, replaces
        Content-Type: application/sdp
    Message Body
        Session Description Protocol
            Session Description Protocol Version (v): 0
            Owner/Creator, Session Id (o): - 21225879 21225879 IN IP4 x.x.x.x
            Session Name (s): -
            Connection Information (c): IN IP4 x.x.x.x
            Time Description, active time (t): 0 0
            Media Description, name and address (m): audio 20827 RTP/AVP 0 2 4 8 18 96 97 98 100 101
            Media Attribute (a): rtpmap:0 PCMU/8000
            Media Attribute (a): rtpmap:2 G726-32/8000
            Media Attribute (a): rtpmap:4 G723/8000
            Media Attribute (a): rtpmap:8 PCMA/8000
            Media Attribute (a): rtpmap:18 G729a/8000
            Media Attribute (a): rtpmap:96 G726-40/8000
            Media Attribute (a): rtpmap:97 G726-24/8000
            Media Attribute (a): rtpmap:98 G726-16/8000
            Media Attribute (a): rtpmap:100 NSE/8000
            Media Attribute (a): fmtp:100 192-193
            Media Attribute (a): rtpmap:101 telephone-event/8000
            Media Attribute (a): fmtp:101 0-15
            Media Attribute (a): ptime:20
            Media Attribute (a): sendrecv
            [Generated Call-ID: d00bf67-6c3188fe@x.x.x.x]

2

Mitel MiVoice Business/MCD/3300 / Re: Basic SPA8000 configuration to connect to MiVB with SIP Trunking

« on: May 06, 2020, 09:54:41 AM »

Hi Ralph,

Ran a SIP trace from the MiVB, currently the SPA8000 is getting a 403 Forbidden from the MiVB with the following reason "399 x.x.x.x "29H Access Barred"", checked COS for PSTN Access over DPNSS and COR access over the route, no problems there. When I attach a SIP softphone using the same credentials I can make calls fine.

Thanks,

Craig

3

Mitel MiVoice Business/MCD/3300 / Basic SPA8000 configuration to connect to MiVB with SIP Trunking

« on: May 01, 2020, 09:28:52 AM »

Hi all,

Picked up a customer with some legacy kit. Moved their PRI over to SIP and their Linksys SPA8000 fail to make a call outbound. From the CCS trace it shows the outbound call over the SIP UA leg with a CIM/CCM of 0 but doesn't show the outbound leg of the call over the SIP Trunking Peer, can see the device making the call using the correct trunk access digit.

Set up a SIP softphone using the same UA and can make calls outbound ok so I don't think its the MiVB (v9.0) configuration, had a look at the SPA8000 and there is tons of options, not sure where to start. If anyone has a basic config that I can start on would be greatly appreciated.

Also note that the SPA8000 is on the same subnet as the MBG which the SIP trunks terminate.

4

Mitel MiVoice Business/MCD/3300 / Re: 112 SIP DECT vs 5624 Wi-Fi Phone - Durability

« on: August 14, 2019, 03:40:16 AM »

Installed many of these devices over the years.

The 5624 are fantastic because it does not need additional infrastructure, however I have seen roaming issues with Cisco Mearki and any Access Points that are not controlled by a central controller, the handsets tend to hold onto an AP right until it has an extremely weak signal and then drop the connection for a second or two while it re-homes. Not necessarily dropping the call but you will notice choppy audio. Best results have been with Aruba and Rukus WiFi setups. One major downfall and I see this a lot is the programmer you need to configure and charge these phones, they tend to go missing and are quite expensive to replace.

The 112 is easy enough to deploy in SOHO setups and because it uses DECT 6.0 the signal is pretty much uninterruptible and has a great range (up to 40 - 50 feet). You can hang up to 20 DECT handsets of one 112 RFP, up to 3 repeaters and handle 5 simultaneous calls. There is a web interface so remote management is easy. The only downside is for large deployments these take some time to set up, but if you use DHCP option 66 and set up a config template you can auto deploy these devices and make mass changes fairly easily.

5

Mitel Software Applications / Re: Mitel No Call History shows up

« on: December 24, 2018, 03:42:03 PM »

Weird thing we found with the 6940 when the call history didn’t show up, we checked the normal COS and Call History records were all ok. But if you pair you mobile to the phone over Bluetooth the call history started appearing, you can forget the pairing and the call history continued to work.


Sent from my iPhone using Tapatalk

6

Mitel Software Applications / Re: Multiple MiVB R9 with one MiCollab 8.1

« on: November 16, 2018, 02:27:34 AM »

Correct, when sharing from the first controller it will share the network elements form. This will then allow the MICollab to sync with the other controllers in the cluster.


Sent from my iPhone using Tapatalk

7

Mitel MiVoice Business/MCD/3300 / Re: Audio burst comes over a 6930 speaker phone when a user is NOT on the phone

« on: November 04, 2018, 04:04:34 PM »

There is a similar issues that has been identified and addressed in firmware version 1.4. Check the fixed issues in the MiVB 9.0 release notes it should have more details on there.

Craig


Sent from my iPhone using Tapatalk

8

Mitel Software Applications / Re: Virtual Nupoint upgrade

« on: November 01, 2018, 05:03:37 PM »

Are the ports out of service on the MIVB? What device type do you have them configured as? E.g. 5020 IP

Sent from my SM-J510FN using Tapatalk

9

Mitel Software Applications / Re: Multiple MiVB R9 with one MiCollab 8.1

« on: November 01, 2018, 05:00:55 PM »

The MiVBs need to be in a cluster with the MiCollab server using FTP to manage changes on both controllers

Sent from my SM-J510FN using Tapatalk