Inbound Caller ID pulling from SIP Trunk IP?

mevans336
Posts: 18
Member Since:
2007-04-11

Hello all,

When HUDLite pulls inbound caller ID info, when the call is ringing, the Caller ID is correct. However, when a call is answered on our main SIP trunk, HUDLite reports that we are connected with extension 208, since the IP address of our SIP trunk starts with 208.

-- SIP/205-0989b6a0 answered SIP/208.x.x.x-b794a130
-- Executing [s@macro-auto-blkvm:1] Set("SIP/205-0989b6a0", "__MACRO_RESULT=") in new stack
-- Executing [s@macro-auto-blkvm:2] DBdel("SIP/205-0989b6a0", "BLKVM/205/SIP/208.x.x.x-b794a130") in new stack

(I replaced the rest of the IP with "x")

If we call in via our Voicepulse trunk, this is what we see and when we answer, the proper external caller ID is displayed.

-- SIP/205-0989b6a0 answered SIP/VPusername--b793f980
-- Executing [s@macro-auto-blkvm:1] Set("SIP/205-0989b6a0", "__MACRO_RESULT=") in new stack
-- Executing [s@macro-auto-blkvm:2] DBdel("SIP/205-0989b6a0", "BLKVM/205/SIP/VPusername--b793f980") in new stack

Any ideas?