[SIPForum-discussion] SIP original A-number

Tue Sep 2 17:46:27 UTC 2008

Correct, if the diversion header was not supported and since we have a call forward always on 111-1111 to CFA 222-2222.
A couple of scenarios would happen depending on the messaging supported by the various network elements.
Scenario 1)  From:  111-1111 To:  222-2222,  (incorrect caller ID is delivered to 222-2222)
Scenario 2)   From 333-3333 To:  222-2222, (most VoIP application platforms would kill the call in this scenario due to the from and to both being PSTN numbers and not owned by the VoIP application, this is for security reasons, anti-spoofing)

In scenario 2, you just need the diversion information there to verify the call is valid, not spoofed, and route advance on diversion header.

________________________________
From: 杨伟 [mailto:shyw13 at gmail.com]
Sent: Monday, September 01, 2008 6:43 PM
To: Singleton, Andrew R.
Cc: discussion at sipforum.org
Subject: Re: [SIPForum-discussion] SIP original A-number

Hi, Singleton

I am not very clear about you case.

In your case, you have three numbers,
caller 333-3333
original callee 111-1111
redirected callee 222-2222
Is this right?

So you add Diversion Header = 111-1111 in the SIP message to show the original callee number.

Is my understanding correct?

Thanks
Richard

2008/8/28, Singleton, Andrew R. <ANDREW.SINGLETON at mcleodusa.com<mailto:ANDREW.SINGLETON at mcleodusa.com>>:

The key is diversion header, your application server needs to be able to route advance on diversion.  I think some do this with history-info but not 100% sure on that one.  We use diversion.

333-3333 = Cell phone from external source

111-1111 = Customers desk phone (find me follow me, or call forward to 222-2222)

222-2222 = customers cell phone

333-3333->111-1111->222-2222

In ISDN world you have:  OCN, original called number, calling party number, called party number and Redirecting number.  In our example:

Calling party number:  333-3333

OCN = 111-1111

Called party number = 222-2222

Redirecting number = 111-1111

SIP:

From = 333-3333

To = 222-2222

Diversion Header = 111-1111 (I believe populated from the ISDN OCN or Redirecting number, not 100% sure here.  Or if not ISDN, as in a IP PBX, this should be populated by the customer prem based equipment)

There are other field but these are the important ones.

The diversion header is the key.  So as long as the customers equipment populates the diversion header information, we are good.

________________________________

From: discussion-bounces at sipforum.org<mailto:discussion-bounces at sipforum.org> [mailto:discussion-bounces at sipforum.org<mailto:discussion-bounces at sipforum.org>] On Behalf Of Jimmy Svensson
Sent: Wednesday, August 27, 2008 9:55 AM
To: discussion at sipforum.org<mailto:discussion at sipforum.org>
Subject: [SIPForum-discussion] SIP original A-number

Hi!

Is there any features in SIP to enable show original A-number? Any special fields that can be used?

We as an operator use SIP-trunking to connect enterprise PBXes and see a demand to display the original A-number when doing an external forwarding. In this case someone calls an extension in the PBX that is forwarded to an external number. A new call leg is created to call this external number, here I want the original A-number to be shows as From but this is not allowed because of A-number-validation in our application server.

Any good solutions/workarounds?

Thanks!

Jimmy Svensson
Network Engineer
Technology Planning

TDC Sverige AB
Box 799
SE-191 27 SOLLENTUNA
Tel +46 8 563 101 23 dir.
Tel +46 8 519 810 00 vxl.
Mobil +46 701 81 01 23
Email jimmy.svensson at tdc.se<mailto:jimmy.svensson at tdc.se>
Web tdc.se<http://tdc.se/>

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

________________________________
NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.

_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org<mailto:discussion at sipforum.org>

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

________________________________
NOTICE: This electronic mail transmission may contain confidential information and is intended only for the person(s) named. Any use, copying, or disclosure by any other person is strictly prohibited. If you have received this transmission in error, please notify the sender via e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20080902/07dd5417/attachment-0002.html>