3300/MediaTrix 1204 FXO gateway help

[cknipe]

Hey guys I was wanting to know if anyone else has ran into these issues. Im using the Mediatrix 1204 to supply a remote site with a few analog lines. At our main site I am using a 3300 CX 9.0 UR1. I have used the document that mitel provided and I am ble to make outgoing calls without a problem.(mitel doc# 06-5177-0009_2.doc)


On inbound calls to the POTS line, the call will ring 2 times and then just disconnect.


ANyone have any ideas why there is a disconnect?

 

[IrwinMFletcher]

It's most likely the negotiation between the two. In the outbound calls, the MediaTrix is making the Offer, in the other case it's the 3300 making the Offer. This will trigger different behaviour between the two. I'd try to get a wireshark trace between the two.

 

[edvac]

cknipe,

I would check your "trunk service assignment" for the SIP trunks. Make sure that you are absorbing '0' digits. Cause it sounds like the Mediatrix is making the call, but when it gets to the Mitel, it is an "INVALID" number.

 

[cknipe]

Yea I called mitel support and went through that with them. After the phone call was over they basically said since it does not show how to config incoming calls in the mitel doc #05-5177-0009_2 that they couldnt really provide assistance. Im kinda dissapointed that the mitel interop doc does not show this and thats thier stance on support.

 

[IrwinMFletcher]

cknipe, SIP is a funny beast. In my opinion they should call it SI, because it's anything but a Protocol. The spec is so loose that different vendors have different implementations so interop is a nightmare.

Back to your problem....as mentioned, I think the best way to find out where the problem is is to find out who is terminating the call, the 3300 or the MediaTrix box. See if you can get a wireshark capture of a call and post the results.

 

[cknipe]

Here is the capture's I provided to mitel. One is an outbound phone call.

http://www.yourfilehost.com/media.php?cat=other&file=inbound_phone_call_mirroring_mediatrix.pcap

http://www.yourfilehost.com/media.php?cat=other&file=Inbound_call_mirroring_Mitel_3300.pcap

http://www.yourfilehost.com/media.php?cat=other&file=outbound_phone_call.pcap

 

[IrwinMFletcher]

On the traces:

Trace A: Doesn't contain a full call, but just an OPTIONS request from the 3300 to the MediaTrix. These are returned as Error 405 which I think is odd. More on that later...

Trace B: This looks like a normal call.

Trace C: Contains no packets pertaining to a voice call (no packets between 10.0.1.224 (the 3300) and 10.0.1.225 (the MediaTrix).

It looks like, is that the MediaTrix isn't handling the OPTIONS request during the call. I ay 'during', but this is just speculation because none of the captures actually show a full call. Trace B doesn't show a BYE, so we still don't know who disconnected the call. I don't think however that the MediaTrix not supporting the OPTIONS would actually tear down the call either, so it leads me to believe that it's something on the 3300 programming side that is causing the failure.

I would try to get a full capture, showing the full SIP transactions for a failed call (someone must tear down the call?).

Also, what happens if you answer the incoming call on the first ring?

 

[cknipe]

I actually cant answer the call on the first ring. I think somewhere inside the mediatrix config is a place to push the inbound call to, though it is no where in the documentation.




When is comes to SIP, what's the verbage for "inbound answer point." You have to use an snmp config tool to manage the device which gives you about 150 different config forms. If I knew some of the wording or verbage to look for it may be a little easier. Though I think i've got management convinced to pony up a couple bucks for me to call mediatrix support.

 

[IrwinMFletcher]

I'm not sure what they call it.

Before you call them I would still try to get a good trace of the problem, if I was them it would be the first thing I would ask for as well. When you're dealing with interop issues, the first reaction is to blame the other guy. To cut to the chase you'll want to be able to show them, "See, it sends this message then disconnects." Who knows, when you get the full call trace it may be Mitel you call.....