SIP Trunk and 503 Service Unavailable

[mightyking]

Hello Everyone,

We have a trunk from Sipelia Genetec server to our CUCM Publisher. The dailplan in the Sipelia sends all calls starting with 120 to our CUCM using the trunk called Cisco. I the packet capture I can see the Sipelia is trying to communicate with out CUCM but an error message stating 503 Service Unavailable. Please find attached the capture file as well as 3 screenshots showing the dilaplan config, 503 Service Unavailable error message and the codecs supported bt Sipelia. We are using G711 and have disabled G722.

Thanks,

MK

[b.winter]

Have you also added a SIP Trunk in CUCM, with the IP of the Sipelia Server?

If yes, also resetet the SIP trunk? Have you checked the logs of CUCM?

--- Please rate this post as "Helpful" or accept as a solution, if your question has been answered ---

[saifuddin.miyaji]

In addition to b.winter's advise, you could also create the sip profile with "options enabled" and apply it to the trunk on the CUCM. This would allow you to see the status of the trunk.

saif

[mightyking]

Thank you guys for taking the time and replying.

Integration with Sipelia allows security people to receive intercom calls from Sipelia on Cisco devices  

A trunk from Sipelia to CUCM has been configured but I don't see the need of configuring a trunk from CUCM to Sipelia as the traffic is always in Sipelia to CUCM direction.  I creaged an application user in CUCM and configured the same user in Sipelia to allow the communication between 2 nodes. Have associated few Cisco devices with the application user and waiting to complet some tests. Will update as soon as I can get someone on the site to do the tests.

Thanks,

MK

[Roger Kallberg · Accepted solution]

Without a trunk in CM the built in security will drop all traffic from the Sipelia system. You’ll have to have a SIP trunk in CM to allow the traffic and you’ll need to set an inbound CSS on it that has access to any needed partitions.

[b.winter · Accepted solution]

How will you expect it to work, when you don't configure the CUCM correctly? Even if you just send call in one direction, you need to configure both systems. In your case, you only have done the config on one system.

You need to add a SIP trunk (with all the correct settings, especially the CSS on the trunk) on CUCM, in there you enter the IP of the Sipelia system. As long as you don't do it, it won't work. Easy as that.

What was your intention with the application user? What should be achieved with this?

[Scott Leport · Accepted solution]

Hi there,

I have never heard of Sipelia, but perhaps this is not a SIP trunk integration which is required here, but rather a third-party SIP device and end user which needs to be added to CUCM configured with digest authentication to the Sipelia system? A similar kind of config to the way the Helios IP Force products integrate with CUCM? 

Pure speculation on my part though and a bit of a stab in the dark based on how I've integrated various other systems with CUCM over the years.

Not exactly the same product, but here are some integrations with 2N which you might be able to gleam something out of:

http://ciscoshizzle.blogspot.com/2015/07/2n-helios-ip-force-intercom-on-cisco.html

https://wiki.2n.com/hip/inte/latest/en/1-pbx/cisco-cucm

[mightyking]

Thank you guys,

All replies were very helpful. By creating the trunk from CUCM to Sipelia everything started working.

Scott,

Your solution was very good as well but I decided to go with creating a trunk in both direction.

Thanks everyone