Should * be able to diferentiate between two voipuser number

ianplain :

Its a shame that there is no standard of how calls are presented , It all down to knowing the querks of each supplier.

True. I'm just pleased its all sorted now.

I am new to Asterisk and this problem describes exactly what I am experiencing except my problem is it is SIP and that is all that my current provider offers. Is there a SIP solution to this?

We have multiple (virtual phone numbers) VoIP over SIP. Currently the calls do come through, but are all grouped together. We need to identify which number the user dialed in order for us to handle the call correctly.

We have checked with our providers and they are sending the DNID information. Here is a sample of the header that we receive:

Code:
<-- SIP read from 204.xxx.xxx.xxx:5060:
INVITE sip:s@xxx.xxx.xxx.xxx SIP/2.0
v: SIP/2.0/UDP 204.xxx.xxxxxx:5060;branch=z9hG4bK-0de0e327814bb58b0ccf4b981e511ba7
f: <sip:1905xxxxxxx@xxx.xxx.xxx.xxx>;tag=4771DE00-D34
t: <sip:1905xxxyyyy@ss.callcentric.com>
i: 171655-3350352051-451874 [!at] xxx.xxx.xxx.xxx (replace the [!at] with a @)
CSeq: 1 INVITE
Max-Forwards: 10


How can we access the to "t:" value through Asterisk or AGI? Important note: I'm new to Asterisk so please be gentle.

Thanks for all help in advance,
Paul

We used the sip accounts to determine what number they had called.

Quote:

exten => SIP_USERNAME_ONE,1,Goto(mainmenu-one,s,1) exten => SIP_USERNAME_TWO,1,Goto(mainmenu-two,s,1)

I agree that using the sip accounts to identify the number that was called will/does work. But, since the information that I see being received does contain the dialed number in the "t:" field in the header, how is that accessible? I know that the sip account is a work around, but since the data is present there shouldn't have to be a hack for it.

Does Asterisk simply ignore this data or am I missing something very simple?

Thanks,
Paul

I found a solution after a many days of searching. I have to give the credit to the user on this site - sorry for violating any link references for this forum but I need to place credit where it is due.

http://forums.whirlpool.net.au/forum-replies-archive.cfm/464741.html

The solution is with the SIP_HEADER function and it does give me the DNIS that I was looking for and saw in the header.

Thanks for all your help and hopefully it will be handy for others,
- Paul