An INVITE form Kazoo contains Contact-URI contains mod_sofia instead of Callee info

[Arne van Balgoijen]

Yealink phones are able to display on the first line the CalleeID and on the second line the CallerID.

Apparently the SIP INVITE message header Contact URI host part is used for that information. On Kazoo the Contact URI Host part contains mod_sofia.

Is there any way to change this to the CalleeID?

Br

Arne

[Arne van Balgoijen]

Apparantly on a standard Freeswitch dialplan this is customisable by adding:

     <extension name="ruri">

      <condition field="destination_number" expression="^ruri$">

       <action application="bridge" data="sofia/${ruri_profile}/${ruri_user}${regex(${sofia_contact(${ruri_contact})}|^[^\@]+(.*)|%1)}"/>

      </condition>

    </extension>

Is there a template dialplan in Kazoo where this could be added, or does this require a custom version of the module https://github.com/2600hz/kazoo/blob/master/applications/ecallmgr/src/ecallmgr_fs_xml.erl, or any other module?

[Arne van Balgoijen]

Anyone any input on this one?

[Arne van Balgoijen]

P-Asserted-Identity: "3255330845" <sip:+3255...@sip.firmtel.net>

    SIP Display info: "3255330845"

    SIP PAI Address: sip:+3255...@sip.firmtel.net

        SIP PAI User Part: +3255330845

        SIP PAI Host Part: sip.firmtel.net

This is how the Yealink currently receives this currently when called with Kazoo, we have to replace the SIP PAI User Part with the Callee info, than if the Phone uses the PAI info it will display the Callee as well.

Br

Arne

[Darren Schreiber]

To ensure that we don't break things on other phones, we would need to find a way to make this a flag you turn on/off on the phone if you want this functionality. That's the only way I can think of to avoid having to figure out what's supported by who, and what the user wants.

I think you are proposing that the From: header remains intact, but the P-Asserted-Identity has different information (originally dialed number / callee). In such a case, In particular, Yealink phones can then display both the originally dialed number and the callers number on the display at the same time. I am not sure what happens to the line which has Caller ID Name. This will need testing I'm sure.

Please file a ticket in the JIRA system with this request.

[Darren Schreiber]

To be clear, this feature does not exist today.

[Dave Singer]

Arme,

If you are seeing "mod_sofia" on the screen of the phone there is something else wrong here. Yealink's documentation on Caller ID says nothing about the contact header. See page 286 of http://www.yealink.com/Upload/T4X/Yealink_SIP-T46G_IP_Phone_Administrator_Guide_V71_60.pdf

The only headers it can be configured to look at for Caller ID are From, PAI, and RPID. It has support for looking at those headers in a preference order depending on which headers are present. I suggest option 4 (PAI-RPID-FROM). PAI is part of the official SIP standard and as part of it's spec it overrides the From header. RPID was a proposal to the SIP standard that was never accepted into the official standard.

FYI "mod_sofia" is in the user part of the Contact URI.

The Yealink phone would display the "Display Name" portion of the URI and maybe the User portion when the "Display Name" is present in the URI of the header it finds (PAI, RPID, FROM). If the "Display Name" is not present it will use the User portion of the URI.

A PAI header example from the  PAI SIP spec:  (https://www.ietf.org/rfc/rfc3325.txt)

P-Asserted-Identity: "Cullen Jennings" <sip:flu...@cisco.com>
The Display Name portion is "Cullen Jennings".

That is all about the Caller ID.

As far as the Callee ID, I don't see anything in the admin guide but It would be using either it's own display name, the user portion of the Request URI, or possibly the user portion of To header.

The default way kazoo has FreeSwitch send the call the user part of the Request URI and To headers is the username of the device. You can change it to e164 or NPA. I'm not sure what would happen when the original dialed number was by a local user dialing like a 4 digit extension.

There is a way to set the user portion of the contact header. Example:

{sip_contact_user=${ruri_user}}sofia/my_profile/12...@192.168.0.1;transport=tcp.

The example that you provided just sets the RURI from the destination user's registered contact. But based on the documentation for the sofia_contact function it would not work the way it is on a regular FS installation. I believe with the kazoo setup FS does not handle any registration stuff. So anything like that would have to be done in the kazoo erlang code. But pretty sure that is not needed for this problem.

Hope this helps. :)

On Wednesday, October 22, 2014 9:32:03 AM UTC-7, Darren Schreiber wrote:

To be clear, this feature does not exist today.

On Wednesday, October 22, 2014 9:31:27 AM UTC-7, Darren Schreiber wrote:

To ensure that we don't break things on other phones, we would need to find a way to make this a flag you turn on/off on the phone if you want this functionality. That's the only way I can think of to avoid having to figure out what's supported by who, and what the user wants.

I think you are proposing that the From: header remains intact, but the P-Asserted-Identity has different information (originally dialed number / callee). In such a case, In particular, Yealink phones can then display both the originally dialed number and the callers number on the display at the same time. I am not sure what happens to the line which has Caller ID Name. This will need testing I'm sure.

Please file a ticket in the JIRA system with this request.

On Thursday, September 11, 2014 3:32:27 AM UTC-7, Arne van Balgoijen wrote:

P-Asserted-Identity: "3255330845" <sip:+32...@sip.firmtel.net>

    SIP Display info: "3255330845"

    SIP PAI Address: sip:+32...@sip.firmtel.net

[Arne van Balgoijen]

Dave,

A late reaction to your note, I was convinced it would have been something we could set ourselves, but have not yet found a way to do it.

We currently do not actually see "mod_sofia" on the Yealinks, but just want to make visible what number was called (calleeID).

I did file an issue: https://2600hz.atlassian.net/browse/KAZOO-3152, so please vote, if you agree.

In the issue I added a pcap of another provider that has this info visible on a Yealink phone.

I suggested to use the contact field in the message, so the contact URI user part contains the CalleeID instead of the current sip:mod_sofia.

Up to now I have not yet found a way to do this.

Br

Arne