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.


Topics - cchaney

Pages: [1]
1
Mitel MiVoice Business/MCD/3300 / SIP trunk
« on: November 23, 2012, 02:22:36 AM »
Hey all -- thanks in advanced for even reading the post.


We just ordered a few SIP trunks from Bandwidth and have our vendor configuring the trunks with our 3300 PBX.

Up to this point, we are still having issues with one way audio -- they can hear us, we cannot hear them.  Test calls are usually placed from my teleworker phone and captures have been done using port mirroring and Wireshark.

Our PBX is NAT'ed behind a Cisco ASA security appliance, which is SIP aware.  From what I can see, it looks like our firewall is properly handling the translations/etc to/from Bandwidth's SIP proxy.

Bandwidth is reporting a ‘Not Acceptable’ from the PBX, from what they have said.



VoIP Flow:

|Time     | 10.1.2.2                              | 68.xxx.xxx.xxx                          |
|         |                   | 216.82.xxx.xxx    |                   
|0.000000000|         INVITE    |                   |                   |SIP From: "C.User" <sip:+281xxxxxxx@10.1.2.2 To:<sip:+1281xxxxxxx@216.82.xxx.xxx
|         |(5060)   ------------------>  (5060)   |                   |
|0.000449000|                   |         INVITE    |                   |SIP Request
|         |                   |(5060)   <------------------  (5060)   |
|0.097827000|                   |         100 Giving a try              |SIP Status
|         |                   |(5060)   ------------------>  (5060)   |
|0.097941000|         100 Giving a try              |                   |SIP Status
|         |(5060)   <------------------  (5060)   |                   |
|4.205087000|                   |         183 Session Progress          |SIP Status
|         |                   |(5060)   ------------------>  (5060)   |
|4.205356000|         183 Session Progress          |                   |SIP Status
|         |(5060)   <------------------  (5060)   |                   |
|19.623845000|                   |         200 OK SDP (g711U telephone-eventRTPType-101)          |SIP Status
|         |                   |(5060)   ------------------>  (5060)   |
|19.624424000|         200 OK SDP (g711U telephone-eventRTPType-101)          |                   |SIP Status
|         |(5060)   <------------------  (5060)   |                   |
|19.672179000|         ACK SDP (g711U telephone-eventRTPType-101)          |                   |SIP Request
|         |(5060)   ------------------>  (5060)   |                   |
|19.672840000|                   |         ACK SDP (g711U telephone-eventRTPType-101)          |SIP Request
|         |                   |(5060)   <------------------  (5060)   |
|26.235692000|         BYE       |                   |                   |SIP Request
|         |(5060)   ------------------>  (5060)   |                   |
|26.236031000|                   |         BYE       |                   |SIP Request
|         |                   |(5060)   <------------------  (5060)   |
|26.346427000|                   |         200 OK    |                   |SIP Status
|         |                   |(5060)   ------------------>  (5060)   |
|26.346695000|         200 OK    |                   |                   |SIP Status
|         |(5060)   <------------------  (5060)   |                   |




Here is the trace from Bandwidth support:

U 2012/11/06 20:32:48.834529 68.xxx.xxx.xxx:5060 -> 216.82.xxx.xxx:5060
SIP/2.0 406 Not Acceptable.
Via: SIP/2.0/UDP 216.82.xxx.xxx;branch=z9hG4bKb2b.d003737.0,SIP/2.0/UDP 67.231.xxx.xxx;branch=z9hG4bKb2b.5dbb3216.3,SIP/2.0/UDP 192.168.37.68:5060;branch=z9hG4bK0bB86c148cbb1cb7710.
Record-Route: <sip:216.82.xxx.xxx;lr;ftag=gK0b07b3aa>,<sip:67.231.xxx.xxx;lr=on;ftag=gK0b07b3aa>.
Warning: 399 10.1.2.2 "19H Reject".
From: <sip:+1919xxxxxxx@192.168.37.68;isup-oli=0>;tag=gK0b07b3aa.
To: <sip:+1281xxxxxxx@67.231.xxx.xxx>;tag=0_2240970064-98773126.
Call-ID: 1863043143_16435119@192.168.37.68.
CSeq: 17638 INVITE.
Contact: <sip:68.xxx.xxx.xxx>.
Server: Mitel-3300-ICP 11.0.1.26.
Content-Length: 0.


Happy Thanksgiving!

2
Mitel Software Applications / UCA / Dynamic Status & Personal Ring Group
« on: May 18, 2012, 04:11:11 PM »
Hello all --

Having issues with UCA and dynamic status.. looks like when I moved to a dynamic status that goes to voicemail, when someone calls my direct number, they go straight to voicemail.. as expected. 

But if I select a dynamic status that is directed to the Personal Ring Group and has certain devices selected (e.g. for In the Office it should ring on desk phone + cell phone.. for Mobile it should just ring on Softphone + cell phone.. Working from Home Office should be offsite extension, softphone, mobile), this does not work.. when someone calls my direct number, it rings all devices (so even if I select Mobile where it should just ring softphone and cellphone, it still rings desk phone, home office phone, softphone, and cellphone).

The UCA desktop application, UCA Android application, and the UCA Web page all show the dynamic status are synced together (all statuses are there with proper devices selected, etc).. I do see a warning in the error log when switching dynamic status but tech said Mitel said that is usual and expected.

MCD 3300 + MAS + applications (desktop + mobile) are all updated to latest revisions available.


Side observation -- our phone tech tried it at their office and said they experience the same thing I mentioned above -- if dynamic status with voicemail redirection is setup, it takes no worries.. when he selects his ring group with various devices, it still rings on all.

We have another employee on the same system that I am on, but with an iPhone.  At first his iPhone had contact sync issues + dynamic status update issues, as reported above.  He noticed his dynamic status were not updating from his desktop application and his mobile application.. the status was there just all his devices were enabled in the mobile application.  He completely removed the application, reinstalled.. this fixed his contact sync issues + his dynamic status issue (from what he says). 

I still do not think this is an iPhone/Android issue because as mentioned, the same issue still exists when using the UCA web client to modify/change the dynamic status / ring group.


Has anyone else experienced this?  If so, do you have a possible solution?

3
Mitel MiVoice Business/MCD/3300 / 5550 IP Console
« on: April 16, 2012, 02:38:56 PM »
What is the current version of the 5550 IP Console software? 


Thanks!

Pages: [1]