Inbound VoIP calls don't ring on Aastras connected to a MER group

[Darren]

Hi There,

I'm having a problem with a MER group containing 6 Aastra 53is and a Snom M3. Since upgrading our Quadro 2X to firmware version 5.1.31, whenever an inbound VoIP call arrives at our Quadro 2X (from the same ITSP as we use - MyNetPhone) the Aastra 53is do not ring, only the Snom M3 rings.

Calls originating from PSTN->ITSP->Quadro 2X ring on all extensions as they did before the firmware upgrade.

Below is an extract from the Quadro 2X system logs that indicates that the problem appears to be an "Unsupported Media Type".

Any help in solving this problem would be greatly appreciated.

Thanks,

- Darren -

18:18:01 Receive SIP message # (27/01/2010 07:18:01:323 GMT) # UDP # 603 bytes # buff size 1 # from: 192.168.13.24:5060 # to: 192.168.13.20:5060

***************************** SIP message buffer start *****************************
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 192.168.13.20:5060;rport=5060;branch=z9hG4bKEPSVBU S0c40965e-32d6-4e1c-a836-6d7676e1a441;received=192.168.13.20
From: "0390182950" <sip:0390182950@125.213.160.81>;tag=1264018680ae75 35ee-5d6a-4ab2-a66e-aa14592d7ebc
To: <sip:LocExt24@192.168.13.20:5060>;tag=3359667618
Call-ID: 26995935334697614_b10ec9a9-38de-4226...ro.listech.com
CSeq: 789 INVITE
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE, PRACK, SUBSCRIBE, INFO
Allow-Events: talk, hold, conference
Server: Aastra 53i/2.2.0.166
Content-Length: 0

***************************** SIP message buffer end ******************************

18:18:01 Try to send SIP message # (27/01/2010 07:18:01:328 GMT) # UDP # 511 bytes # buff size 1 # from: 192.168.13.20:5060 # to: 192.168.13.24:5060

***************************** SIP message buffer start *****************************
ACK sip:LocExt24@192.168.13.24;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.13.20:5060;rport;branch=z9hG4bKEPSVBUS0c40 965e-32d6-4e1c-a836-6d7676e1a441
To: <sip:LocExt24@192.168.13.20:5060>;tag=3359667618
From: "0390182950" <sip:0390182950@125.213.160.81>;tag=1264018680ae75 35ee-5d6a-4ab2-a66e-aa14592d7ebc
CSeq: 789 ACK
Call-ID: 26995935334697614_b10ec9a9-38de-4226...ro.listech.com
User-Agent: Epygi Quadro SIP User Agent/v5.1.31 (QUADRO-2X)
Max-Forwards: 70
Content-Length: 0

***************************** SIP message buffer end ******************************

[davrays]

Can you look at the INVITE message sent to that phone (it should appear before the 415 Unsupported Media Type message)? What codec do you see there (they are listed in the end of the SIP message)?
Do you have those codecs active on the phone?

[Darren]

Hi davrays,

Thanks for your reply and I apologise for not responding earlier.

I have located the INVITE message but cannot work out what codec it is requesting so I have attached the log with the hope that you can locate it for me?

The problem Aastra 53i phones have been provisioned directly by the Quadro 2X so the codec settings will be whatever the 2X has configure them to.

One thing I did notice was that the automatic upgrading of the firmware for the Aastra phones failed when I upgrade the Quadro 2X firmware to 5.1.31, so I have manually upgrade the firmware on one of the 53is to the recommended version but with the same result.

Thanks and best regards,

- Darren -

[davrays]

Which fw versions do you have on those Aastra phones?

It is still not clear to me what makes the Aastra phones reject the call. The media parameters Quadro sends are completely acceptable (there are codec G729 and :"telephon-event" used), and I need to test here to understand why Aastra has problems with those media params. You can try to workaround this by selecting PCMA/PCMU on the MER extension.
Also can you please put the extension with "LocExt21" into the same MER group for a moment and make a call to that group? I can see in the log that LocExt21 answers to a call with exactly the same media parameters, and it is interesting whether it will answer to the call being in MER group...

I'll try to find some info and get back to you.

Best regards,
David

[Darren]

Hi davrays,

Thanks for your response to my posting.

For some reason the Aastra firmware is not being automatically upgraded on the Aastra handsets by the Quadro 2X with the 5.1.31 firmware. To test if the handset firmware was the cause of the problem, I manually upgraded two handsets to firmware 2.3.1.26 as recommended in the 5.1.31 firmware release notes. One handset was in the MER group (LocExt28) and one was not in the MER group (LocExt21), but this made no difference. All other handsets are still on firmware 2.2.0.166

PCMA/PCMU codecs are already enabled on the MER extension but are second and third in the priority list after G729. I tried moving G729 down to position 3, but I still get the same result.

I added "LocExt21" to the MER group and made an external VoIP call that goes to the MER extension and "LocExt1" did not ring either - only “LoctExt23” rings.

I certainly appreciate your help at looking into this problem and hope you may have some more suggestions for me?

Thanks and best regards,

- Darren -

[KSComs]

Darren did you reset the handsets after doing the upgrade ?

If not redeploy and let the Quadro auto configure ... hopefully it will deploy the right config file as necessary...

Another thing to try is with another ITSP - I use http://www.bbpglobal.com/aust/default.php for testing.... so that might assist seing as there sip server works with the Quadro without a hitch and free - as it may be an ITSP problem and a coincidence that it doesnt work now.

Just a though mate...

Kev