[Extended Mode]

I operate a SIP Proxy server. Often, to assign PSTN numbers to users I alias the PSTN number to their UserID. In this instance, the user has a PBXnSIP box configured with domain.local

 

e.g.

 

My user may be sip:1000@sip.provider.com - but I alias a PSTN phone number to that e.g. sip:00123123@sip.provider.com

 

There is a trunk configured on the PBX to provider.com that registers using user 1000.

 

If I call sip:00123123@sip.provider.com calls come in as;

 

INVITE sip:1000@192.168.236.20:5060 SIP/2.0

From: "Test" <sip:2000@sip.provider.com>;tag=7349e455

To: <sip:00123123@sip.provider.com>;tag=29226

 

Where sip:00123123@sip.provider.com is the alias. I've tried a few different expressions. Does the pattern take into account the sip: prefix, the domain - or just the user portion?

 

Whats the most simple way to say, match the user portion (in this case 00123123)?

[DDI Tagging]

I'll reply to myself. I think I've figured out a way with the Snom 360's. I guess using other phones, the From "Name" <sip:11@ss.c> would need to be changed?

 

Or not. The Snom 360's don't display the bits between the " " in the To: Header..

[DDI Tagging]

I'll reply to myself. I think I've figured out a way with the Snom 360's. I guess using other phones, the From "Name" <sip:11@ss.c> would need to be changed?

[DDI Tagging]

The way to do this is to use the address book. The PBX changes the display name according to what is in the address book, also for the To-header

 

They use Snom 360's. Can I configure them to display both the From and To so they know how to answer the phone?

 

 

Like I said - I can always do something on the ISDN gateway or on an Asterisk box, but would prefer to avoid that. At the same time - I don't know if there's sufficient demand to have it written as an add-on.

 

If the phone can't display the "To", If the address book matches both the `From` and the `To`, perhaps some control over what is sent as the display name in the From.

 

To use your example;

 

INVITE sip:123@192.168.1.2;line=123 SIP/2.0

From: "Company A" <sip:2121231234@localhost>

To: "Company A" <sip:9781231234@localhost>

P-Asserted-Identity: "2121231234" <sip:2121231234@localhost>

[DDI Tagging]

I have a customer who really needs the 'DDI Tagging' functionality found on other PBX systems. DDI Tagging basically rewrites the CLI so it displays a given name when a specific DDI is called, this allows the operator to answer the phone with the correct greeting.

 

e.g.

 

A call comes in on ISDN for 100, 100 is Company A's DDI - the phone displays "Company A" and the operator answers appropriately.

A call comes in on ISDN for 105, 105 is Z Inc's DDI - the phone displays "Z inc." and the operator answers appropriately.

 

Is there any way of achieving this at the current time?

 

At the minute I'm assigning a different identity to Snom phones and using the LED function keys. My problem is they have a lot of DDIs like this and their former system (BT Versatility) supports DDI tagging. (Google suggests a lot of other systems do to).

 

I'm a little bit stuck with this which basically leaves me two options, neither of which are desirable.

 

1) I can use a different ISDN gateway that supports multiple SIP accounts. I can then configure routing on the Gateway to say, DDI 100 use Sip Account A. I would then configure the gateway to send the SIP UserID as the CLI. This is a pain.

 

2) I can sit an Asterisk Box in front of PBXnSIP or run it on Linux on a non-standard port, and trunk all calls in this way, re-write the CLI, then forward to PBXnSIP.

 

Any suggestions?