IPIPGW SIP trunk to Mitel fails

Unanswered Question
May 27th, 2007

Hi

I need to setup a SIP trunk to Mitel. I have an IPIPgw providing SIP-H323 conversion. calls from the Mitel to CCM work fine, but calls from CCM to Mitel get dropped. debug on IPIPGW shows that SIP Invite gets sent to Mitel, but SIP 480 message gets sent back. the phone that we are trying to call does in fact ring once before the 480 comes back, and the debug shows the correct numbers going across in the invite.

all help appreciated!

SIP debugs for outbound call from IPIPGW to Mitel (names removed):

1w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 10.68.64.49:5060;branch=z9hG4bK2DE4B

From: "xxx xxx" <sip:[email protected]>;tag=246FF58B-1D2A

To: <sip:[email protected]>

Date: Fri, 08 Mar 2002 04:26:43 GMT

Call-ID: [email protected]

Supported: 100rel,timer

Min-SE: 1800

Cisco-Guid: 14282785-1227084061-1460142080-3232269354

User-Agent: Cisco-SIPGateway/IOS-12.x

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER

CSeq: 101 INVITE

Max-Forwards: 70

Remote-Party-ID: "xxx xxx" <sip:[email protected]>;party=calling;screen=yes;privacy=off

Timestamp: 1015561603

Contact: <sip:[email protected]:5060>

Expires: 180

Allow-Events: telephone-event

1w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 10.68.64.49:5060;branch=z9hG4bK2DE4B

Timestamp: 1015561603

From: "xxx xxx" <sip:[email protected]>;tag=246FF58B-1D2A

To: <sip:[email protected]>;tag=MitelICP_2360753296-56820724

Call-ID: [email protected]

CSeq: 101 INVITE

Content-Length: 0

1w0d: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 480 Temporarily Unavailable

Via: SIP/2.0/UDP 10.68.64.49:5060;branch=z9hG4bK2DE4B

Timestamp: 1015561603

From: "xxx xxx" <sip:[email protected]>;tag=246FF58B-1D2A

To: <sip:[email protected]>;tag=MitelICP_2360753296-56820724

Call-ID: [email protected]

CSeq: 101 INVITE

Contact: <sip:10.222.254.11>

Content-Length: 0

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
teodorgeorgiev Mon, 05/28/2007 - 00:31

I am 80% sure that this is due to codec negotiation problems.

Check the configured codecs all along the path.

Unfortunately I do not see the Cisco offering any codecs to Mitel in the INVITE message.

There should be a set of a=rtpmap lines with the preferred codecs.

g.sperryn Mon, 05/28/2007 - 03:39

yeah my first thought was codecs too.

codec is set as g711a for inbound and outbound dialpeers.

what would make an IPIPgw not send codec info?

Paolo Bevilacqua Mon, 05/28/2007 - 14:15

Hi,

I would try setting codec transparent for ip-to-ip gw. It is strange it is not sending a= lines in sip invite. Peraphs if you enable debug cch323 it would be possible to see what the CM is sending.

Paolo Bevilacqua Tue, 05/29/2007 - 10:05

Hi,

I see that you are also using a GK and that is possibly complicating the issue. In the debug, looks like CCM is not specifying a codec:

1w0d: //105/00D9F0215708/SIP/Info/sipSPIGetCallConfig: preferred_codec set[0] type :No Codec bytes: 0

Compare that with a successful GK/GW call where a codec is specified:

http://cisco.com/en/US/tech/tk1077/technologies_configuration_example09186a00800a9a56.shtml

You may need to check CCM/GK configuration and take traces on CCM. Also, if you repost in "IP telephony" forum you may get a better answer as there are more CCM experts in there.

Actions

This Discussion