Good evening guys,
My new forum place, my first questions here.
I come from a more traditional PBX world for the past several years administering Siemens HiPath4000 PBX (softswitch since latest version).
Cisco UCM is quite a new concept for me, VoIP from the ground up. It doesn't always makes enough sense but must admit it is a good concept.
Brief overview of the LAB architecture:
Linux Host ---> VMWare Workstation ---> ESXi ---> CUCM 18.104.22.16800-37
Call processing service on.
Linux Host IP: 10.10.80.103
ESXi IP: 10.10.80.104
CUCM IP: 10.10.80.105
On the Linux Host I have installed Ekiga SIP softclient.
CUCM has SIP Security Profile configured with Digest Authentication. Profile successfully applied to Ekiga SIP softclient.
Ekiga SIP softclient is configured with the physical nic MAC address.
NOTE: I have used different SIP softclients - same results.
When I try to register Ekiga in CUCM registers successfully.
However, CUCM populates incorrect IP for Ekiga.
The IP is 192.168.236.1. This is VIRTUAL IP from vmnet1 virtual adapter on the Linux host. This virtual adapter also has its own different MAC address.
I have cleared CUCM's arp cache with utils network arp delete IP with no avail.
I have learnt how to trace the call. From the trace file I obtained, in the SIP registration can be found:
REGISTER sip:10.10.80.105 SIP/2.0
CSeq: 305 REGISTER
Via: SIP/2.0/UDP 10.10.80.103:5060;branch=z9hG4bKba9c9413-4a04-e311-83c5-84a6c8d35b03;rport
Authorization: Digest username="Ekiga", realm="ccmsipline", nonce="kYzZzVpXYNSC/zFrnGqrgkG/vamfLpc/", uri="sip:10.10.80.105", algorithm=MD5, response="36d51a9b63b97140dae1a45f0b9e957b"
Contact: <sip:firstname.lastname@example.org>;q=1, <sip:email@example.com>;q=0.667, <sip:firstname.lastname@example.org>;q=0.334
Apparently the Ekiga SIP client advertise THREE Contact addresses, out of which the Second (192.168.236.1) and Third(172.16.80.1) are Virtual IP address.
CUCM decides to register Ekiga on the second virtual IP (192.168.236.1) instead of the first physical IP address (10.10.80.103).
Any idea what can I do to force CUCM to prioritize registration on the first - physical IP address ?