UC540 NO INCOMMING SIP CALLS

[ealvarez]

Hi, I have a problem with a UC540, i can outgoings call with the sip trunk but it´s imposible incoming call.

This is debug ccsip messages

Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

　

　

No Inactive Message Discriminator.

　

Console logging: disabled

Monitor logging: disabled

Buffer logging: level debugging, 22 messages logged, xml disabled,

filtering disabled

Exception Logging: size (4096 bytes)

Count and timestamp logging messages: disabled

Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 304 message lines logged

Logging Source-Interface: VRF Name:

Log Buffer (5000000 bytes):

000290: Jun 5 18:33:35.231: %SYS-5-CONFIG_I: Configured from http by cisco on 192.168.10.66

000291: Jun 5 18:33:35.371: %SYS-5-CONFIG_I: Configured from http by cisco on 192.168.10.66

000292: Jun 5 18:33:40.151: %SEC-6-IPACCESSLOGP: list 104 denied tcp 88.26.221.114(15183) -> 192.168.0.80(443), 1 packet

000293: Jun 5 18:33:41.419: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(49627) -> 192.168.0.80(443), 1 packet

000294: Jun 5 18:33:42.683: %SEC-6-IPACCESSLOGP: list 104 denied tcp 84.127.226.179(18805) -> 192.168.0.80(443), 1 packet

000295: Jun 5 18:33:43.947: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(13182) -> 192.168.0.80(443), 1 packet

000296: Jun 5 18:33:49.491: %SEC-6-IPACCESSLOGRL: access-list logging rate-limited or missed 119 packets

000297: Jun 5 18:33:53.183: %SEC-6-IPACCESSLOGP: list 104 denied tcp 88.26.221.114(15192) -> 192.168.0.80(443), 1 packet

000298: Jun 5 18:33:54.455: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(49629) -> 192.168.0.80(443), 1 packet

000299: Jun 5 18:33:55.763: %SEC-6-IPACCESSLOGP: list 104 denied tcp 84.127.226.179(18818) -> 192.168.0.80(443), 1 packet

000300: Jun 5 18:33:56.987: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(13184) -> 192.168.0.80(443), 1 packet

000301: Jun 5 18:34:04.543: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

INVITE sip:856924825@62.43.206.102:56214 SIP/2.0

Via: SIP/2.0/UDP 94.23.83.177:5060;branch=z9hG4bK55dcb427;rport

Max-Forwards: 70

From: "956059747" <sip:956059747@94.23.83.177>;tag=as15ae1fa9

To: <sip:856924825@62.43.206.102:56214>

Contact: <sip:956059747@94.23.83.177:5060>

Call-ID: 62aab4b526eb4e397b659c2766a1206f@94.23.83.177:5060

CSeq: 102 INVITE

User-Agent: VozGlobal

Date: Wed, 05 Jun 2013 16:31:40 GMT

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH

Supported: replaces, timer

Remote-Party-ID: "956059747" <sip:956059747@94.23.83.177>;party=calling;privacy=off;screen=no

Content-Type: application/sdp

Content-Length: 272

v=0

o=root 1516626963 1516626963 IN IP4 94.23.83.177

s=VozGlobal

c=IN IP4 94.23.83.177

t=0 0

m=audio 14058 RTP/AVP 18 8 101

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

a=sendrecv

000302: Jun 5 18:34:04.547: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Sent:

SIP/2.0 400 Bad Request - 'Invalid Host'

Via: SIP/2.0/UDP 94.23.83.177:5060;branch=z9hG4bK55dcb427;rport

From: "956059747" <sip:956059747@94.23.83.177>;tag=as15ae1fa9

To: <sip:856924825@62.43.206.102:56214>;tag=8F9F8-2485

Date: Wed, 05 Jun 2013 16:34:04 GMT

Call-ID: 62aab4b526eb4e397b659c2766a1206f@94.23.83.177:5060

CSeq: 102 INVITE

Allow-Events: telephone-event

Reason: Q.850;cause=100

Server: Cisco-SIPGateway/IOS-12.x

Content-Length: 0

　

000303: Jun 5 18:34:04.631: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

Received:

ACK sip:856924825@62.43.206.102:56214 SIP/2.0

Via: SIP/2.0/UDP 94.23.83.177:5060;branch=z9hG4bK55dcb427;rport

Max-Forwards: 70

From: "956059747" <sip:956059747@94.23.83.177>;tag=as15ae1fa9

To: <sip:856924825@62.43.206.102:56214>;tag=8F9F8-2485

Contact: <sip:956059747@94.23.83.177:5060>

Call-ID: 62aab4b526eb4e397b659c2766a1206f@94.23.83.177:5060

CSeq: 102 ACK

User-Agent: VozGlobal

Content-Length: 0

　

000304: Jun 5 18:34:06.263: %SEC-6-IPACCESSLOGP: list 104 denied tcp 88.26.221.114(15203) -> 192.168.0.80(443), 1 packet

000305: Jun 5 18:34:07.463: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(49631) -> 192.168.0.80(443), 1 packet

000306: Jun 5 18:34:08.791: %SEC-6-IPACCESSLOGP: list 104 denied tcp 84.127.226.179(18828) -> 192.168.0.80(443), 1 packet

000307: Jun 5 18:34:10.031: %SEC-6-IPACCESSLOGP: list 104 denied tcp 77.229.64.164(13187) -> 192.168.0.80(443), 1 packet

Thanks,.

[paolo bevilacqua · Accepted solution]

The NAT device that you use do not work for SIP.

You can use a cisco router for NAT, or give UC500 a public IP address.

[ealvarez]

Hi Paolo,

     I have the UC540 direct to the router, i don´t understand your solution, how i can give a public IP address to UC540?

thanks.

[Ayodeji Okanlawon]

The error you are getting suggest that the sip traffic has been sent to an IP address that doesnt exist on your uc520. The ip address 62.43.206.102 is not configured on your UC520. That means as Paolo suggsted your NAT configuration is not working. You need to fix that.

Sent:

SIP/2.0 400 Bad Request - 'Invalid Host'

Via: SIP/2.0/UDP 94.23.83.177:5060;branch=z9hG4bK55dcb427;rport

From: "956059747" <956059747>;tag=as15ae1fa9

To: <856924825>;tag=8F9F8-2485

Date: Wed, 05 Jun 2013 16:34:04 GMT

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[ealvarez]

OK, but it´s possible with the UC540 nat?

thanks

[paolo bevilacqua]

aokanlawon wrote:
 No, I dont think your UC540 can do NAT for sip traffic.

Absolutely it can. It is a Cisco router after all.

[Ayodeji Okanlawon]

Paolo I said that because it looks like most people use ASA to do the NAT when UC5XX series are deployed. I may be wrong. Thanks for correcting that idea

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[paolo bevilacqua]

aokanlawon wrote:
 Paolo I said that because it looks like most people use ASA to do the NAT when UC5XX series are deployed. I may be wrong. Thanks for correcting that idea

Nothign wrong with that, But I have deployed tens of CMEs and UC500s without ever using ASA, always had ecellent results technically, and economically without compromising any security.

[paolo bevilacqua]

     I have the UC540 direct to the router, i don´t understand your solution, how i can give a public IP address to UC540?

Set the ISP router in bridge mode. Configure UC500 WAN port as it was ISP router.

[ealvarez]

Thank you very much for yours help, it will try it and I tell you.

[ealvarez]

Hi,

     My configuration is this:

UC540 LAN 192.168.10.1

UC540 WAN 192.168.0.80

PUBLIC IP:62.43.206.102  Cisco EPC3825 EuroDocsis 3.0 Gateway

I need you said me how i can configure in UC540 Nat pool and Nat static Mapping.

Thank you very much for yours help.

[paolo bevilacqua]

As above, configure Fa0/0 for public IP as per ISP instrucions.