Inbound SIP call Failure

Answered Question
Sep 3rd, 2009

Hello,

I have a SIP trunk from Voxitas into a UC520. I have managed to get outbound calls to work, but Inbound calls fail.

The deb ccsip output is below.

000705: Sep  3 18:46:44.199: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 209.40.224.167:5060;branch=z9hG4bK16d29a95;rport
From: "+14692583232" <sip:[email protected]>;tag=as5995d869
To: <sip:[email protected]>
Contact: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 102 INVITE
User-Agent: NetLogic Switch v3.2.3
Max-Forwards: 70
Date: Thu, 03 Sep 2009 18:47:41 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Type: application/sdp
Content-Length: 291

v=0
o=root 20313 20313 IN IP4 209.40.224.167
s=session
c=IN IP4 209.40.224.167
t=0 0
m=audio 61150 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv

000706: Sep  3 18:46:44.203: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Invalid Host'
Reason: Q.850;cause=100
Date: Thu, 03 Sep 2009 18:46:44 GMT
From: "+14692583232" <sip:[email protected]>;tag=as5995d869
Allow-Events: telephone-event
Content-Length: 0
To: <sip:[email protected]>;tag=9CE8F8-39
Call-ID: [email protected]
Via: SIP/2.0/UDP 209.40.224.167:5060;branch=z9hG4bK16d29a95;rport
CSeq: 102 INVITE
Server: Cisco-SIPGateway/IOS-12.x


000707: Sep  3 18:46:44.235: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 209.40.224.167:5060;branch=z9hG4bK16d29a95;rport
From: "+14692583232" <sip:[email protected]>;tag=as5995d869
To: <sip:[email protected]>;tag=9CE8F8-39
Contact: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 102 ACK
User-Agent: NetLogic Switch v3.2.3
Max-Forwards: 70
Content-Length: 0

I have configured everything from the CCA. Please let me know if I am missing something. I appreciate your response.

Also, I have attached the Running Config from my UC below. Let me know if I am missing Something.

Thank you all in anticipation!

Regards,

Prasanna Singaraju

Attachment: 
I have this problem too.
0 votes
Correct Answer by Saurabh Verma about 7 years 2 months ago

Hi Prasanna,

The DSL router would be required to translate network addresses in the SIP messages. It is probably doing so in one direction (from UC 500 to the SIP Provider) and the SIP provider has registered DSL router's public IP as the SIP endpoint. Can you check with the DSL router vendor, whether there is a way to configure SIP enabled NAT on the DSL router? If not, you may have to use another product that can support this functionality.

Thanks,

Saurabh

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Saurabh Verma Thu, 09/03/2009 - 12:30

Hi Prasanna,

In your setup, would you happen to know which device has IP address 99.68.202.246? Looks like the UC 520 is getting an INVITE that's meant for this IP address. Also from your configuration, I noticed that the wan  fastethernet interface 0/0 is configured with IP address 192.168.4.113 which I think is connecting to an Internet router. Is the router doing any SIP NAT translations?

-Saurabh

psingaraju Thu, 09/03/2009 - 13:14

Hello Saurabh,

The internet router is simply passing traffic along. No NATting!


The public IP is that of the DSL modem/router.

I am trying to get it to NAT to 192.168.4.113, with no luck. any pointers would be great helpful.

Regards,

Prasanna

Correct Answer
Saurabh Verma Thu, 09/03/2009 - 13:21

Hi Prasanna,

The DSL router would be required to translate network addresses in the SIP messages. It is probably doing so in one direction (from UC 500 to the SIP Provider) and the SIP provider has registered DSL router's public IP as the SIP endpoint. Can you check with the DSL router vendor, whether there is a way to configure SIP enabled NAT on the DSL router? If not, you may have to use another product that can support this functionality.

Thanks,

Saurabh

psingaraju Thu, 09/03/2009 - 13:27

Damn! I did not think about something silly. I made the change and forgot to reset the DSL modem.

The reset did it, I foget motorola doesn't make products as sturdy as Cisco does.

Great it works now...Thanks Saurabh!

Regards,

Prasanna

Actions

This Discussion