Wrong CallerID in calls originated via click to dial

[vmtelecom]

When making calls via click-to-dial, call is rejected by SIP provider with response 403 Forbidden auth ID because of resulting SIP invite has following From line format: From: "my_ext_geo_number" sip:[email protected];tag=

What could be the cause of this issue?

[blak3r]

The code for click to dial is really short. Others have mentioned similar issues. The AMI command is originate.

Search issues for createCall.php and you should find the advice I gave others. Let me know if you find a solution.

Sent via mobile

On Dec 20, 2013, at 4:19 AM, vmtelecom [email protected] wrote:

When making calls via click-to-dial resulting SIP invite has following From line format: From: "my_ext_geo_number" sip:[email protected];tag=

What could be the cause of this issue?

— Reply to this email directly or view it on GitHub.

[vmtelecom]

I have set Route CID to one of our geo numbers on outbound route used by callinize, but then we cannot tell which extension initiated the call since in asterisk cdrs there are destination numbers and source number identical for calls originated via click to dial.

[blak3r]

Pretty annoying. I'm not too familiar with CDR logs etc. Have you looked at the code? It's really simple... and only a few variables to mess around with.

See this page: http://www.voip-info.org/wiki/view/Asterisk+Manager+API+Action+Originate

You could experiment by using telnet and pasting in command payloads even.

On Mon, Dec 30, 2013 at 1:14 PM, vmtelecom [email protected] wrote:

I have set Route CID to one of our geo numbers on outbound route used by callinize, but then we cannot tell which extension initiated the call since in asterisk cdrs there are destination numbers and source number identical for calls originated via click to dial.

— Reply to this email directly or view it on GitHubhttps://github.com/blak3r/yaai/issues/169#issuecomment-31359329 .