cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2084
Views
0
Helpful
32
Replies

call between two cucm

kingstdz
Level 1
Level 1

Hi 

we have two cucm on each site, with gateway ,linked by wan

my gw is on h323, we have declared sip trunk between site, and RP but give us 503 error ,, 5060 port is not blocked, 

how to fix that and if there is other solution to permit call between via GW voice of each side.

thanks

1 Accepted Solution

Accepted Solutions

The call no pass because sip trunk is down remote error 503 in log is there service unavailable

View solution in original post

32 Replies 32

b.winter
VIP
VIP

Don't you see the error by yourself?
H.323 is not the same as SIP...

GW uses H.323 but in CUCM you use SIP.

How do you expect the GW to answer on SIP messages, if it is configured with H.323?

My advice: Change the GW to use SIP.
H.323 shouldn't be used anymore.

So you have two sites with a CM at each and these sites have connectivity with each other via a WAN connection? If so all you need to do is to configure a SIP trunk on each of the CMs that points to the other CM and use normal call routing, aka route patterns to pass calls to the remote location, you don’t need to involve and gateway for this. If I’m completely off the mark here please get back with a more detailed outline of your system landscape so that we can better address your needs.



Response Signature


HI thanks for, you match watch i am doing, sip trunk on each side, but i get error 503 on each side, port 5060 is not blocked, and each CM is pinging, where it can be the mistakes?

thanks

What is your exact setup?
Are the CUCM directly conncted via the SIP trunk? CUCM <--> CUCM
Or is the GW in between? CUCM <--> GW <--> CUCM

"503" in CUCM indicates, that the IP adress is not the correct one. So, the other side uses a different IP address than configured in the SIP Trunk setting.

cucm A--sip trunk ---cucmB

our sid A: Cucm --GW---WAN

side B: Cucm --GW--WAN

GW A ping GW B and vice versa

CUCM A, and B reachable by ping, we have give side B our @ip and vice versa.

 

And your problem is now between CUCM A and CUCM B?
What is the IP of CUCM A?
What is the IP of CUCM B?
Which IP address is configured in the SIP Trunk in CUCM A?
Which IP address is configured in the SIP Trunk in CUCM B?

2023_03_01_10_53_.png

here the capture with wireshark, it stuck on side A with 503 (may verify port 5060? but is not blocked!!)

Nobody said something, that the port is blocked?!
Maybe the problem is not on the SIP trunk, have you checked the complete call log with RTMT? Without a trace of the call or access to the environment, it's hard to say where the problem is...

in A sip trunk with ip of B

in B sip trunk with ip of A

Do you have multiple CM nodes on each site? If so have you checked the check box Run on all nodes on the SIP trunk on each side and reset the trunk in each CM?

image.png



Response Signature


kingstdz
Level 1
Level 1

is there any news please help me. thanks

As already written, you need to send logs from CUCM or the GW of an example call.
As long as you don't do that, it will be hard for anybody to help you.

You have to provide the information to help you, we don't have access to your setup.

kingstdz
Level 1
Level 1

here is log 

2023/03/02 06:33:07.594|SIPL|0|TCP|IN|ip cucm sub|5060|SEP549FC6298F4D|ip phone|51591|2,100,251,190307.508^ip phone^*|61149029|549fc629-8f4d0025-0dc32182-754d62ee@ip phone^5193bde200105000a000549fc6298f4d^*|INVITE
2023/03/02 06:33:07.603|CC|SETUP|37624060|37624061|XXXX|XXXXYYYY|XXXXYYYY|5193bde200105000a000549fc6298f4d|*
2023/03/02 06:33:07.604|SIPL|37624060|TCP|OUT|ip cucm sub|5060|SEP549FC6298F4D|ip phone|51591|2,100,251,190307.508^ip phone^SEP549FC6298F4D|61149031|549fc629-8f4d0025-0dc32182-754d62ee@ip phone^00000000000000000000000000000000^*|503 Service Unavailable
2023/03/02 06:33:07.608|SIPL|37624060|TCP|IN|ip cucm sub|5060|SEP549FC6298F4D|ip phone|51591|2,100,251,190307.509^ip phone^*|61149032|549fc629-8f4d0025-0dc32182-754d62ee@ip phone^5193bde200105000a000549fc6298f4d^*|ACK
2023/03/02 06:33:07.609|CC|REJECT|37624060|37624061|XXXX|XXXXYYYY|XXXXYYYY|5193bde200105000a000549fc6298f4d|*|1459617833

This doesn't help.
Download the full trace in RTMT and upload it here.