Outbound Caller ID Problem

[spidersden]

Hello,

 

I have had an issue reported to me by one of our users today. The problem is that if an entry is added to your personal address book via the PBX web interface, and then you dial that address book entry from the web interface, the caller ID of the remote party shows their own phone number (instead of ours).

 

In other words, dialing an address book entry with a phone number of 1-234-567-8901 from 1-423-xxx-xxxx shows 1-234-567-8901 on the remote party's caller id instead of our 1-423-xxx-xxxx number.

 

This only happens if the little green phone icon is clicked from the call column of the usr_adrbook.htm page. Using the the phone icon on the "Call Logs" or "Missed Calls" pages works properly. If we use the address book via the phone UI, then caller id is properly displayed on the receiving party's phone.

 

An interesting, but probably bad, side affect of this is that if we use the web address book dial link to call a cell phone, then we get dropped directly into that persons voicemail, because the remote carrier thinks that the user is calling themselves. This would be the same for any carrier or pbx configured to put a user in their mailbox if they call their own number.

 

To reproduce the problem:

1. 
    
   
2. Log into the SnomONE web interface as an extension account
   
3. Click the "Lists" tab
   
4. Click the "Address Book" link
   
5. Add an entry
   
6. Use the green phone icon to initiate a call to the remote party. The remote party will see their own phone number on their caller id
   

 

The only thing I'm noticing as a major difference with web dialing between the Call Log page (usr_callog.htm) and the Address Book page (usr_adrbook.htm), is that the call link is formulated a little differently.

 

Link from Call Log looks like:

http://pbx.our.domain/remote_call.htm?dest=1423xxxxxxx

Using this first link properly displays CID on the remote phone.

 

Link from Address Book looks like:

http://ip.of.the.pbx/remote_call.htm?user=241%40our.domain&dest=1423xxxxxxx

Using this link does not properly display CID on the remote phone.

 

Notice that the properly working link is using the FQDN for the pbx whereas the non-working uses the IP address.

 

 

Thank you,

~Scott

Edited October 27, 2011 by spidersden

[spidersden]

 

Link from Address Book looks like:

http://ip.of.the.pbx/remote_call.htm?user=241%40our.domain&dest=1423xxxxxxx

Using this link does not properly display CID on the remote phone.

 

Notice that the properly working link is using the FQDN for the pbx whereas the non-working uses the IP address.

 

For what it's worth, if I copy the URL from the Address Book call link, and change the IP address to the FQDN of the PBX, the caller ID does display properly at the remote party.

 

In other words, manually changing this url:

http://ip.of.the.pbx/remote_call.htm?user=241%40our.domain&dest=1423xxxxxxx

to this url:

http://pbx.our.domain/remote_call.htm?user=241%40our.domain&dest=1423xxxxxxx

results in proper caller id display for the remote party.

 

Any suggestions on how to work around this?

 

Product: SnomONE Blue 2011-4.2.1.4025 (Linux)

[pbx support]

Do you have the SIP log from the PBX for these 2 cases?

[spidersden]

Do you have the SIP log from the PBX for these 2 cases?

 

Yes. I have sent them via PM to you.

Edited October 28, 2011 by spidersden

[spidersden]

I appreciate the quick response.

 

The INVITEs sent on the trunk has an issue in the 'bad' case. Both the "From" & "To" have the same value. Looks like the provider does not look at the "P-Asserted-Identity" header. So, can you please change the "Trunk->Edit->Remote Party/Privacy Indication:" to "Remote-Party-ID" and re-do the test. We move around the header contents a bit and that probably would take care of the caller-id.

 

As you recommended in PM (quoted above), I set "Remote Party/Privacy Indication" to Remote-Party-ID and re-tested. That appears to have corrected our problem. I've included your suggestion here in hopes of helping other forum members in the future.

 

Thank you for your help and a great product.

~Scott