CUCM Trunk sip to isp provider without CUBE

[Gilles Dellaccio]

Hi,

I try to configure a trunk sip with a provider without cube.

I can to make outgoing call without problem, it work fine!

But when i initiate a incoming call, my CUCM return the SIP message "404 Not found".

In my trunk sip configuration, in the inbound call section, i have apply a CSS who can access to a translation pattern:

- i receive from the provider 214097015@xyz.com

- the created translation pattern 214097015, his affect CSS can access internal phone, translate to the phone 1022 (called transf. pattern).

- actually the significant digit for the inbound call of the trunk sip is "all" (but i have test with 10, 9, 4 receive digit and modified the translation pattern, digit but same problem).

I don't understand why the cum return the SIP msg 404.

Somebody have a idéa?

Misconfiguered translation pattern? (i don't but think this, but...)

Thank a lot.

[Gilles Dellaccio]

Yes, the dns resolution work fine.

but, in the trunk sip configuration, when i replace the ip address of the SIP destination address by the hostname "pbx.eqinoxe.com". i can't call a external phone.

admin:utils network host pbx.eqinoxe.com
Local Resolution:
Nothing found

External Resolution:
pbx.eqinoxe.com has address 185.48.253.8

admin:utils network ping pbx.eqinoxe.com
PING pbx.eqinoxe.com (185.48.253.8) 56(84) bytes of data.
64 bytes from xdsl.185.48.253.8.srvc.fr (185.48.253.8): icmp_seq=1 ttl=53 time=36.1 ms

--- pbx.eqinoxe.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3015ms
rtt min/avg/max/mdev = 19.258/32.287/38.206/7.590 ms

[Gilles Dellaccio]

hi,

Yes i have a Fortigate firewall for the NAT

i'don't work today and tomorrow, i must verified the firewall's configuration Friday.

thanks.

[Ayodeji Okanlawon]

Gilles,

Apologies for my late reply.

Looking at your CUCM logs, I see that your publisher IP address is 192.168.100.205.

Now the RURI((request URI) from the INVITE from your ITSP , this is the field that CUCM uses to route the call is this..

INVITE sip:214097015@93.17.11.122:5060;transport=udp SIP/2.0

The host portion of the RURI looks to be a NAT address and not the CUCM IP address..

From a trace of a working outbound call, we can see this..

INVITE sip:0214097015@185.48.253.8:5060 SIP/2.0
Via: SIP/2.0/TCP 192.168.100.205:5060;branch=z9hG4bK275c13b036250

The VIA shows where CUCM wants the response to this request, so we see its correct IP address..

You need to sort this out. Looks like its a NAT issue. The request must have the IP address of the CUCM