Unknown IP addresses referenced during call setup

[MatsW]

I've got 7.1.7139.0 installed on a XP Pro system, and during call setup there's a reference to an unknown IP address (192.168.100.44) in the Server Activity Log:

192.168.100.23 is the 3CX server, and 192.168.100.44 is some dynamic address but it's nowhere in DCHP or DNS. Does anyone know what the log at 17:55:52.313 means?

17:55:52.313 [CM503001]: Call(81): Incoming call from +4684456920@(Ln.10002@NETatONCE privat) to <sip:[email protected]:5060>
17:55:52.298 [CM503012]: Inbound out-of-office hours rule (unnamed) for 10002 forwards to DN:64
17:55:52.298 Looking for inbound target: called=+46856474000; caller=+4684456920
17:55:52.157 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected]:5060;rinstance=524dcb27faa5c86e SIP/2.0
Via: SIP/2.0/UDP 217.10.96.45;branch=z9hG4bKa399.250a13f7.0
Via: SIP/2.0/UDP 213.50.88.8:5060;branch=z9hG4bK-yxa-qzvswuxivgwvnwlqovbiwg-UAC-ozuw9wotuheg_i9nnbncxpg
Via: SIP/2.0/TCP 213.50.88.12:5060;branch=z9hG4bK-d8754z-72210b104d0ac536-1---d8754z-;received=213.50.88.12;rport=37808
Max-Forwards: 68

 

[SY]

Does PBX provide only this part of incoming invite? :shock:

17:55:52.157 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected]:5060;rinstance=524dcb27faa5c86e SIP/2.0
Via: SIP/2.0/UDP 217.10.96.45;branch=z9hG4bKa399.250a13f7.0
Via: SIP/2.0/UDP 213.50.88.8:5060;branch=z9hG4bK-yxa-qzvswuxivgwvnwlqovbiwg-UAC-ozuw9wotuheg_i9nnbncxpg
Via: SIP/2.0/TCP 213.50.88.12:5060;branch=z9hG4bK-d8754z-72210b104d0ac536-1---d8754z-;received=213.50.88.12;rport=37808
Max-Forwards: 68

 

[leejor]

You don't have an extension 64 attached to the PBX? The inbound rules seem to think that they have to send an incomming call of to that extention at that IP. Are you using single line or multi line ATA's on the network? Can you ping that IP from a computer connected to the same network. Start, Programs, accessories, command Prompt...."ping 192.168.100.44 " see if you get a response.

 

[MatsW]

1) I've already made sure that 192.168.100.44 didn't exist by pinging it yesterday. "44" indicates that this is a dynamic address. The thing is that this is a new install and this machine had a dynamic IP address before the install, so I can't say if it had 192.168.100.44 before I changed it to static 192.168.100.23

2) Extension 64 is the Ring Group that the Voip line calls on an incoming call

3) Now when I look in the log then I can see that I get a different behaviour. The line where 192.168.100.44 was referenced has now changed to

08:24:40.021 [CM503001]: Call(11): Incoming call from +4684456920@(Ln.10002@NETatONCE privat) to <sip:[email protected]:5060>

It seems like some cache somewhere has been updated so that the "44" address is not referenced, but neither ping nor nslookup returned any data for 192.168.100.44 yesterday so I don't understand where this address could have come from. I also know that I did a ipconfig /flushdns yesterday on the server but the problem remained.
Unfortunatly the log from yesterday is now gone.

 

[leejor]

So it's working now then?

 

[MatsW]

Yes, it is. But where did the address come from (seemed to be the dynamic address the server machine had before installation)