SIP From header - howto rewrite it?

42 views
Skip to first unread message

Claas Hilbrecht

unread,
Feb 10, 2022, 9:38:57 AMFeb 10
to sipxcom-users
Hi,

I tried to setup CLIP no screening with easybell (https://www.easybell.de). I ordered the package "Office Komplett Trunk 10 inkl. Fair Flat S" and installed a fresh CentOS (CentOS Linux release 7.9.2009 (Core)) and the sipXecs Release 21.04 release. I enabled "CLIP no screening" within the easybell system. After trying a lot of different combination I found that easybell needs the caller id just as "plain text" inside the From header (see below). I managed this get the wanted caller id if I add the wanted caller id number in the "First Name" or "Last Name" field. The wanted caller id is also present as <sip:wantedcallerid@sip...> but easybell seems to ignore this. Since using the "First Name" or "Last Name" field is not what I really want I wonder if there's an option to apply a regex for specific SIP header fields to rewrite the From header with the content of the <sip:wantedcallerid@sip...> entry. Or is there any other way of getting the desired behaviour?

"2022-02-10T11:40:22.228000Z":434:OUTGOING:INFO:tk.example.com:Thread-48:00000000:sipxbridge:"Sent SIP Message :\n----Remote Host:192.168.33.42---- Port:
 5060----\nACK sip:03012...@sip.easybell.de;user=phone SIP/2.0\r\nCall-ID: 6c09aed6-9f0b...@192.168.88.50-0\r\nMax-Forwards: 70\r\nFrom: \"030
 9988770\" <sip:03099...@sip.easybell.de>;tag=4907591905455862171\r\nTo: <sip:03012...@sip.easybell.de;user=phone>;tag=5FAF8798-6204F99F0000C496-96D2F70
0\r\nVia: SIP/2.0/UDP 192.168.88.10:5080;branch=z9hG4bKf688db25d12bc0292ebbdfa8791a7fae393739\r\nCSeq: 2 ACK\r\nRoute: <sip:192.168.33.42:5060;transport=udp;
lr>\r\nUser-Agent: sipXecs/xxxx.yyyy sipXecs/sipxbridge (Linux)\r\nContent-Length: 0\r\n\r\n--------------------END--------------------\n"
-> 030998877 -> This is the main number of my SIP trunk, which misses the last 0

"2022-02-10T11:42:32.294000Z":724:OUTGOING:INFO:tk.example.com:Thread-92:00000000:sipxbridge:"Sent SIP Message :\n----Remote Host:192.168.33.42---- Port:
 5060----\nACK sip:03012...@sip.easybell.de;user=phone SIP/2.0\r\nCall-ID: 3378c8d7-8d44...@192.168.88.50-0\r\nMax-Forwards: 70\r\nFrom: \"0309988770\"
 <sip:03099...@sip.easybell.de>;tag=7823807881622606601\r\nTo: <sip:03012...@sip.easybell.de;user=phone>;tag=4D6F4090-6204FA1F000EE48B-96F31700\r\n
 Via: SIP/2.0/UDP 192.168.88.10:5080;branch=z9hG4bKcc2d564d1f0df5457ff0eda701c187ff393739\r\nCSeq: 2 ACK\r\nRoute: <sip:192.168.33.42:5060;transport=udp;
 lr>\r\nUser-Agent: sipXecs/xxxx.yyyy sipXecs/sipxbridge (Linux)\r\nContent-Length: 0\r\n\r\n--------------------END--------------------\n"
-> 0309988770 -> This is the wanted caller id

Any help or ideas would be great!

Matt Keys

unread,
Feb 18, 2022, 10:25:11 AMFeb 18
to sipxcom-users
Caller ID can be changed at the user, user group group, or gateway level.

Claas Hilbrecht

unread,
Feb 19, 2022, 3:46:21 AMFeb 19
to sipxcom-users
I'm aware of the different possibilities to set the caller id. But that didn't answer my original question. I think that the way easybell handels the extracting of the caller id is not optimal at least. What would be great is something like the regex rewritte feature off a patton gateway.
Reply all
Reply to author
Forward
0 new messages