# Zoom callerid param not working on android devices

**URL:** <https://devforum.zoom.us/t/zoom-callerid-param-not-working-on-android-devices/75459>\
**Category:** Meetings\
**Created:** [September 6, 2022, 10:15am UTC](https://devforum.zoom.us/t/zoom-callerid-param-not-working-on-android-devices/75459 "2022-09-06T10:15:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![irealunknown27](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/irealunknown27/32/41112_2.png) [@irealunknown27](https://devforum.zoom.us/u/irealunknown27)\
**Post date:** [September 6, 2022, 10:15am UTC](https://devforum.zoom.us/t/zoom-callerid-param-not-working-on-android-devices/75459/1 "2022-09-06T10:15:55Z")

</div>

I am Initiating Zoom phone call from web browser using hyperlink where I have a use case. I need to pass calIerid parameter in the URI scheme to initiate outgoing call from zoom user’s custom/group number instead of the assigned zoom number. So the callerid parameter [i](https://www.lifepo4golfcartbattery.com/)s mandatory (see [here](https://marketplace.zoom.us/docs/guides/zoom-phone/outbound-call/)).

```auto
zoomphonecall:+XXXX?callerid=+YYYY

```

The above URI scheme works from desktop web app and in iOS devices but when I use the same from web android it opens the zoom app but says invalid phone number however `zoomphonecall:+XXXX` this works fine in all devices.

Is there any work around for this ?

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [September 6, 2022, 9:23pm UTC](https://devforum.zoom.us/t/zoom-callerid-param-not-working-on-android-devices/75459/2 "2022-09-06T21:23:03Z")

</div>

Hi @irealunknown27 I think this may be a bug as we have [another customer](https://devforum.zoom.us/t/callerid-parameter-in-zoom-phone-uri-scheme-does-not-work-in-android-devices/75208) reporting this whereas our tech and service engineering team says this is unexpected behavior.

Can you please open up a support ticket with this issue? Share your account id, this thread, and screenshots of the behavior.

Thanks!
