Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
10098
Views
0
Helpful
16
Replies

SIP Trunk Provider says UC520 replying with "500 internal server error" in response to inbound call

Go to solution
mcastrigno
Level 1
Level 1

‎02-18-2009 02:09 PM - edited ‎03-21-2019 12:57 AM

I am trying to set up a SIP trunk DID. The calls do no go through, when a trace is performed the SIP Trunk Provider says UC520 replying with "500 internal server error" in response to inbound call.

Is this a generic message that has lots of possible sources or can this tell me anything?

thanks

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
Marcos Hernandez
Level 8
Level 8
In response to mcastrigno

‎02-18-2009 04:34 PM

CCA 1.9 adds a voice source group for security purposes, that makes the UC500 accept calls ONLY from the configured Proxy server under the SIP Trunk tab. This is put in place to avoid toll fraud (by blocking calls from anonymous sources).

The CLI for that voice source group is as follows:

!
voice source-group CCA_SIP_SOURCE_GROUP
access-list 2
translation-profile incoming SIP_Incoming

!

access-list 2 remark CCA_SIP_SOURCE_GROUP_ACL
access-list 2 remark SDM_ACL Category=1
access-list 2 permit a.b.c.d
access-list 2 deny   any

!

where a.b.c.d is the IP of the proxy.

What was happening here, is that the UC500 was not receiving SIP signaling from that particular IP, but a different one (a 4.x.x.x IP from Level3). this is very common in the SIP world, where ITSP's resell service from wholesale providers.

By adding the 4.x.x.x subnet to the access-list, signalign from that wholesale provider is now allowed:

!

access-list 2 remark CCA_SIP_SOURCE_GROUP_ACL
access-list 2 remark SDM_ACL Category=1
access-list 2 permit a.b.c.d

access-list 2 permit 4.0.0.0 0.0.0.255
access-list 2 deny   any

!

Adding specific subnets to this "allowed list" via the CCA GUI is an enhancement that we will need to incorporate. I will take this up to my team for consideration. That way, CLI won't be required to fix this rather common situation.

Marcos Hernandez
Technical Marketing Engineer
Cisco Systems, Inc.

View solution in original post

0 Helpful
16 Replies 16

Go to solution
Marcos Hernandez
Level 8
Level 8

‎02-18-2009 02:34 PM

I would like to take a look at your full "debug ccsip mess" output and also your full configuration. Since it may have confidential information, please email it to me at marchern@cisco.com. We will post our findings on this thread.

Thanks,


Marcos Hernandez
Technical Marketing Engineer
Cisco Systems, Inc.

0 Helpful

Go to solution
mcastrigno
Level 1
Level 1
In response to Marcos Hernandez

‎02-18-2009 02:51 PM

the cli says "SIP Call messages tracing is enabled"

I made a call in (tried to) where is the output of that trace?

thanks

0 Helpful

Go to solution
Marcos Hernandez
Level 8
Level 8
In response to mcastrigno

‎02-18-2009 03:03 PM

Use this command:

"terminal monitor"

and you will see console output on your Telnet/SSH session. Make sure you have enough buffer space to go back and capture all the messages.

Marcos Hernandez
Technical Marketing Engineer
Cisco Systems, Inc.

0 Helpful

Go to solution
mcastrigno
Level 1
Level 1
In response to mcastrigno

‎02-18-2009 03:16 PM

figured out the debug - used "terminal monitor."

I have sent you the output as well as the running configuration.

thanks

0 Helpful

Go to solution
Marcos Hernandez
Level 8
Level 8
In response to mcastrigno

‎02-18-2009 04:34 PM

CCA 1.9 adds a voice source group for security purposes, that makes the UC500 accept calls ONLY from the configured Proxy server under the SIP Trunk tab. This is put in place to avoid toll fraud (by blocking calls from anonymous sources).

The CLI for that voice source group is as follows:

!
voice source-group CCA_SIP_SOURCE_GROUP
access-list 2
translation-profile incoming SIP_Incoming

!

access-list 2 remark CCA_SIP_SOURCE_GROUP_ACL
access-list 2 remark SDM_ACL Category=1
access-list 2 permit a.b.c.d
access-list 2 deny   any

!

where a.b.c.d is the IP of the proxy.

What was happening here, is that the UC500 was not receiving SIP signaling from that particular IP, but a different one (a 4.x.x.x IP from Level3). this is very common in the SIP world, where ITSP's resell service from wholesale providers.

By adding the 4.x.x.x subnet to the access-list, signalign from that wholesale provider is now allowed:

!

access-list 2 remark CCA_SIP_SOURCE_GROUP_ACL
access-list 2 remark SDM_ACL Category=1
access-list 2 permit a.b.c.d

access-list 2 permit 4.0.0.0 0.0.0.255
access-list 2 deny   any

!

Adding specific subnets to this "allowed list" via the CCA GUI is an enhancement that we will need to incorporate. I will take this up to my team for consideration. That way, CLI won't be required to fix this rather common situation.

Marcos Hernandez
Technical Marketing Engineer
Cisco Systems, Inc.

0 Helpful

Go to solution
Barry Hunsinger
Level 1
Level 1
In response to Marcos Hernandez

‎06-03-2009 02:15 PM

I am having the exact same issue. I am runningcca 2.0. how do I implement this fix?

0 Helpful

Go to solution
Maulik Shah
Level 5
Level 5
In response to Barry Hunsinger

‎06-03-2009 04:17 PM

Check the tip added at link below:
https://supportforums.cisco.com/docs/DOC-9830

That would help if you are seeing the same behavior as documented on this thread.

0 Helpful

Go to solution
bross
Level 1
Level 1
In response to Marcos Hernandez

‎03-23-2010 02:43 PM

I'm eperiencing the same problem with not being able to receive calls on a SIP trunk, no problems with outbound. I'm using a UC540 and CCA 2.2 (2). My provider (EtherSpeak) gave me an IP for the SIP proxy server with no other information, user/pass not needed. I've tried everything in this thread with no luck so far, all help would be appreciated.. thanks

0 Helpful

Go to solution
joe.weinstock
Level 1
Level 1
In response to bross

‎03-23-2010 03:25 PM

We recently had a similar issue with a UC540 with a generic sip config that had worked on previously installed UC520's.  Upgraded the UC540 from 8.0 to 8.01 and that resolved the issue.

0 Helpful

Go to solution
bross
Level 1
Level 1
In response to joe.weinstock

‎03-23-2010 03:30 PM

I'm on 8.0 now, will try the upgrade to 8.01 and see if that helps.. Thanks Joe

Barry

0 Helpful

Go to solution
bross
Level 1
Level 1
In response to bross

‎03-24-2010 11:01 AM

I upgraded the UC540 to 8.0(1), and still having the same issue, I can make outbound calls over the SIP trunk, but no incoming.. Like I said previously, I've attempted all the fixes in this thread, but still in the same situation.. I have also configured the UC540 both from CCA 2.2.2, and from the CLI, each time starting from a default configuration, same results each time..

0 Helpful

Go to solution
Maulik Shah
Level 5
Level 5
In response to bross

‎03-24-2010 05:02 PM

Please gather the logs as identified in section 1 on link below and post to the thread - be sure to mask any passwords or other sensitive information (pvt msg if you do not want to post this)

https://supportforums.cisco.com/docs/DOC-9830

Minor note - maybe best to start a new thread on this topic so as to not confuse with the original poster's question

0 Helpful

Go to solution
mcastrigno
Level 1
Level 1

‎02-18-2009 05:35 PM

Thanks Marcos - couldn't have done it without you!

0 Helpful

Go to solution
mcastrigno
Level 1
Level 1

‎03-24-2010 06:24 PM

Maulik,

I am the orignal poster and appreciate that this thread has been expanded.

I am very interested is learning this persons resolution as it is very common that users have only this message from ISPs to work with.

I look forward to reading your responses to his logs and config.

Thank you,

mcastrigno

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents