Caller ID 1.0.10.39 (SOLVED)

#1

I still can’t get my outbound caller ID to show anything other than unknown on the new firmware.

Is anyone else experiencing this?

#2

I can set it on the trunk and it’ll work, but I can’t get the global in general setting or the custom extension caller ID to go.

#3

If it is a registered trunk, enable “Send PAI Header” or “send PPI Header” in the “Advanced Settings” of the trunk. That did the trick for me.

#4

If the above doesn’t work, go to SIP Settings/ToS and enable “Trust Remote Party ID” and “Send Remote Party ID”. That worked for me.

#5

I experience the same problem with caller ID. If I setup “Send PAI Header” or “send PPI Header” the Caller ID is working. If I setup “Trust Remote Party ID” and “Send Remote Party ID” is also working.
The problem is that with either solution incoming calls gets disconnected. The setup I have is calls answered by IVR, I get the prompt and I dial an extension, the call is flashing on the phone display and hangs up.

#6

dbana:
Catch packet on UCM. there will be info who cancel call. If this is UCM you need check syslog, if external operator ask them why they close it.

#7

It is my understanding that this is a bug in the firmware and will be fixed in the next update

#8

Same here. None of methods described above help. My extensions continue to be treated as anonymous by partner’s asterisk

#9

I received notice on an open ticket this would be resolved in a soon to be released .40 firmware.

The Send PAI TEI user=phone worked on my system to resolve the issues as a work around.

warm regards
Jeff

#10

Did you configure user=phone in extension, or trunk, or both? Just tried this (also with Send PAI checked in trunk settings), did not help.

Thanks in advance.

[quote=“VoIPCanada, post:9, topic:13997”]I received notice on an open ticket this would be resolved in a soon to be released .40 firmware.

The Send PAI TEI user=phone worked on my system to resolve the issues as a work around.

warm regards
Jeff[/quote]

#11

I’m having the same problem. All my outbound calls are displayed as anonymous. None of the methods described here solved my problem.
When will the next firmware be released? And will this issue be fixed with that release?

#12

The BETA is available 1.0.10.42 which helps but doesn’t completely fix.

I am able to leave PAI and PPI header unchecked
if I put a number in the “from user” on the trunk I get that.
if I leave “from user” blank it will pull the extension callerID

#13

I recently had to setup sip trunks with Bulkvs for 911 services. The trunks were registered, and even though I had the caller id number in the From User field, BulkVS saw the call coming from the registered trunk username
123456_15555555555. I had to go to Advanced settings check the box for “Send PIA Header” and then enter my caller ID there instead in order to use the 922 and 933 test number with their service.