transferring external call via AA

[wiper01]

When transferring external pstn call (number A) via Auto Attendant be pressing "1" (number B ) to another external pstn number (number C), only the number B is shown on the screen C. But i need to show the number A.

 

PSTN <-SS7-> call agent <-SIP-> SNOM

 

Can all advise?

[pbx support]

I assume this is a call from an associated cell phone. Generally, PBX sends the ANI of the extension(number B ) or the domain/trunk ANI when making outbound calls. But depending on the trunk settings you can probably see the original caller id too. The INVITE sent out from the PBX should show what numbers are sent in the headers.

[wiper01]

These calls are made from any external pstn numbers.

Outgoing INVITE contained Message headers From: number_A, To: number_C, PPI (or PAI, depending on the trunk settings): number_B.

But the IAM contaiend only Calling party number (number_B ) and Called party number (number_C)... where redirection?

I think that the case in the absence of diversion message in INVITE.

[Vodia PBX]

It is a general problem. Many many many providers will not allow you to show A. This is because they are so much afraid about caller-ID spoofing.

[wiper01]

Actually, I'm the same provider and I'm trying to solve the problem of my client.

We've connect another ip pbx (BroadWorks) to our PSTN call agent, and everything works as expected (see att).

divertion_call_BWKS.zip

And you may compare with SNOM call flow.

divertion_call_SNOM_pass.zip

[Vodia PBX]

snom ONE (well in the standard configuration) keeps the from and to-headers the same. IMHO that is in accordance with the idea that the IETF had originally. In other words: From and To is what the user sees and they are not used for routing or billing purposes.

 

P-Asserted-Identity is used by the PBX to indicate who is paying for the call, and the user in there should be used for authentication purposes. But the PBX also supports ICID, which IMHO is extremly easy when it comes to billing (because the provider does not bill the local user on the system, but the trunk). Unfortunately, not too many people seem to use it.

 

In order to provide some evidence that this is not a spoofed call, the PBX uses the header "Related-Call-ID", which contains the Call-ID of the original call. The PBX is a B2BUA and changes the caller-ID for a redirected call. As a provider, if you provide service for both original and diverted call, you may check if the caller-ID has been spoofed or not (IMHO a great value to a client).

[wiper01]

i think that SNOM should construct redirected INVITE with Diversion header, in accordance with

 

http://tools.ietf.org/html/rfc5806#section-3.1

 

but it doesn't.

 

the call agent we used uses Diversion header in order to construct ISUP field Redirecting number.

 

[Vodia PBX]

Well, the PBX uses the header in certain cases e.g. when redirecting to an external mailbox. But not in the case of forking the call to the cell phone. IMHO it is debatable if this is a diversion, because the desktop phones might also be ringing at the same time. But I dont see how a Diversion header would hurt, so maybe we need to add this header as well.

[wiper01]

It's very usefull function for our customer and its last thing which stops them from purchasing a SNOM ONE (blue or green).

So, in what time frame you may add this header?

Thanks!

[Vodia PBX]

It will not make it into the next release. I would say the one after that will be maybe in 3 months. But regardless we should try with head builds to see how it works in the real life (beta versions), that could happen in two weeks timeframe.

[wiper01]

ok, ll wait for beta

[pbx support]

In the latest v4 (2011-4.2.1.4025), for a different reason/customer, we introduced a "RFC3325(custom)" to keep the "From" and the "P-Asserted" headers the same. Probably you can try that and see if that suffices your need. Otherwise, as you mentioned, wait for the beta.