[asterisk-dev] [Code Review] ast_callerid restructuring

[Klaus Darilion]

Am 11.06.2010 00:13, schrieb rmudgett at digium.com:
> struct ast_party_id {
> 	struct ast_party_name name;
> 	struct ast_party_number number;
> 	struct ast_party_subaddress subaddress;
> 	char *tag;
> };

In Austria it is common in ISDN (and SS7) to signal 2 CLIs - which 
usually have different presentations (user provided and network provided):

< Calling Number (len=15) [ Ext: 0  TON: National Number (2)  NPI: 
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
1 <                           Presentation: Presentation permitted, user 
number not screened (0)  '69911160036' ]
1 < [6c 08 21 83 31 32 35 33 39 37]
1 < Calling Number (len=10) [ Ext: 0  TON: National Number (2)  NPI: 
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
1 <                           Presentation: Presentation allowed of 
network provided number (3)  '125397' ]

Currently Asterisk can not handle this and only 1 CLI is available. Also 
SIP can have multiple CLIs (multiple RPID/PAI, or 1 CLI in From and 1 
CLI in PAI - see Table 27 in Q.1912.5).

Maybe "struct ast_party_id" should be extended to have a second CLI:

struct ast_party_id {
	struct ast_party_name name;
	struct ast_party_number number;
	struct ast_party_number2 number2;
	struct ast_party_subaddress subaddress;
	char *tag;
};

I do not know how this 2 CLIs influences the subaddresses.

regards
Klaus