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 - lcorriero

Pages: [1]
1
MiVB 8.0 SP3 - would like to know if there is an easy way to show DNIS after inbound call is answered via key or COS, etc.

I have COS setup to show DNIS while phone is ringing, but would like it to stay after answered with CID info as well if possible.

Thanks!

2
Hi All, we are trying to move our Level3 SIP trunk from our Fortinet Firewall w/ NAT (too many one way audio issues to count) to the recommended setup of MBG/Proxy - Essentially this should be an easy once since SIP Peer is preexisting and mostly working on VMCD we only spun up MBG Cluster and then select it as Proxy then point Level3 Hunt Group to MBG WAN IPs. Initially this works fine for inbound calls and has been working this way for outbound for some time; however, when we do some inbound call load testing, we eventually start getting random hangups and then see SIP/SIPSm warnings in the VMCD logs -  stating "The SIP link Level3-1 has failed with cause: ServerErrResp - response code 503 (Service Unavailable)Far end possibly overloaded or down for maintenance. The link will be retried in 1 seconds." It then comes back up a second later and we can get inbound calls thru. Wireshark on MBG shows the 503 from the VMCD to the MBG stating Reason: SIP;text="Pending SLOWSTART REINVITE conversion";cause=503. Any comments/assistance is appreciated.

3
Mitel MiVoice Business/MCD/3300 / MCD TFTP Issue
« on: August 17, 2017, 04:06:46 PM »
Hi all, we have an older VMCD 6.0 SP1 - recently we ran into an issue where any 53XX phones that used option 125 pointing to the VMCD for TFTP/ICA would take much longer to download TFTP bin files if not fail altogether. Most, if not all, of these phones are in remote sites over VPN tunnels. Oddly enough, when we point TFTP to MBG, phones boot w/ TFTP more consistently, but still take longer than normal, frequently hanging on TFTP main and then HTML App Upgrade. We have checked network ports w/ firewall and network groups and cannot see anything being blocked since most policies are wide open. We do see the phones establish a connection during TFTP process to UDP 20001 multiple times, but its as if the TFTP process gets stuck, perhaps in "TFTP autonegotiation process" w/ MCD - I am aware you can set block size on MBG, which when lowered from 4096 to 1024 does speed up TFTP boot. Our concern is a bigger issue with VMCD since we cannot manually adjust TFTP block size. Any suggestions/comments appreciated.

Pages: [1]