19 Sep
2013
19 Sep
'13
2:14 p.m.
Wondering what others are doing / looking for any tips for the best handling of caller ID
in this scenario.
Call flow -
UA >> Proxy >> Asterisk >> Proxy >> Carrier
Carrier only reads caller ID by 'From header'
Asterisk is only used for media functions / b2bua and not user aware.
UA username is not a DID but rather some other string, such as 'dan(a)domain.com'com'.
Goal is to use DID for caller ID, but I like to avoid modifying the 'From
header'.
Any thoughts?
[cid:image001.gif@01CEB53F.854769A0]
19 Sep
19 Sep
3:13 p.m.
Daniel,
It's a common problem. The simplest solution - especially if you don't
want to modify the From header - is to use one of the headers that
superecedes From: P-Asserted-Identity, or Remote-Party-ID (deprecated
draft, but very widely used).
Almost all commercial gateways and softswitches prefer them in this
order of precedence: PAI, RPID, From.
-- Alex
On 09/19/2013 02:14 PM, Daniel W. Graham wrote:
Wondering what others are doing / looking for any tips
for the best
handling of caller ID in this scenario.
Call flow –
UA >> Proxy >> Asterisk >> Proxy >> Carrier
Carrier only reads caller ID by ‘From header’
Asterisk is only used for media functions / b2bua and not user aware.
UA username is not a DID but rather some other string, such as
‘dan(a)domain.xn--com-to0a.
Goal is to use DID for caller ID, but I like to avoid modifying the
‘From header’.
Any thoughts?
dan-sig2
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
3:25 p.m.
My issue is I have 1 carrier that doesn't support PAI or RPID for caller ID. Second
carrier supports RPID but not PAI. Still waiting verification from the others.
This definitely seems like a big mess, I'd prefer to use PAI since it follows active
RFC but the lack of support is surprising.
I'm assuming my two options I'm left with are using DID as usernames to avoid From
header changes, or modifying From header.
If I'm forced to modify From header, where would be the place to do so with least
negative affects?
All CDR is performed on Asterisk.
UA >> Proxy >> Asterisk >> Proxy >> Carrier
-----Original Message-----
From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org]
On Behalf Of Alex Balashov
Sent: Thursday, September 19, 2013 3:14 PM
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] Caller ID using From header
Daniel,
It's a common problem. The simplest solution - especially if you don't want to
modify the From header - is to use one of the headers that superecedes From:
P-Asserted-Identity, or Remote-Party-ID (deprecated draft, but very widely used).
Almost all commercial gateways and softswitches prefer them in this order of precedence:
PAI, RPID, From.
-- Alex
On 09/19/2013 02:14 PM, Daniel W. Graham wrote:
Wondering what others are doing / looking for any tips
for the best
handling of caller ID in this scenario.
Call flow -
UA >> Proxy >> Asterisk >> Proxy >> Carrier
Carrier only reads caller ID by 'From header'
Asterisk is only used for media functions / b2bua and not user aware.
UA username is not a DID but rather some other string, such as
'dan(a)domain.com'com'.
Goal is to use DID for caller ID, but I like to avoid modifying the
'From header'.
Any thoughts?
dan-sig2
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
21 Sep
21 Sep
8:16 a.m.
2013-09-19 21:25, Daniel W. Graham skrev:
My issue is I have 1 carrier that doesn't support
PAI or RPID for caller ID. Second carrier supports RPID but not PAI. Still waiting
verification from the others.
This definitely seems like a big mess, I'd prefer to use PAI since it follows active
RFC but the lack of support is surprising.
I'm assuming my two options I'm left with are using DID as usernames to avoid
From header changes, or modifying From header.
If I'm forced to modify From header, where would be the place to do so with least
negative affects?
All CDR is performed on Asterisk.
UA >> Proxy >> Asterisk >> Proxy >> Carrier
You can use the uac-module to change the From-header:
http://kamailio.org/docs/modules/stable/modules/uac.html
More specific the function: uac_replace_from
I use this for normalizing the format from my carriers and to my
carriers (to the format they expect) so all calls from my Asterisks use
the same format, regardless of carrier used for the call.
Make sure you only call uac_replace_from ONCE. From the doc:
"Known limitations: The “uac_replace_*” functions can only be run once
on the same SIP request. Try to save needed changes in a pseudovariable
and apply them once."
/Johan
4168
days inactive
4170
days old
3 comments
3 participants
participants (3)
-
Alex Balashov -
Daniel W. Graham -
Johan Wilfer