01-10-2018 10:37 PM - edited 03-17-2019 11:55 AM
Hello,
For some reason SBC does send within INVITE message the IP Address of SIP Client [private IP] instead of
SBC signalling IP.
Example:
Client SIP Host IP: 192.168.58.1
SBC Outside SIP Signalling IP: 199.150.1.1
Adjacency Peer IP: 166.34.245.231
Via: SIP/2.0/UDP 1199.150.1.1
From: “3660110” <sip:3660110@192.168.58.1>;tag=199.150.1.1+1+56c....
To: <sip:1201123456987@166.34.245.231;user=phone;phone-context=unknow
Desired SIP Invite From Field
From: “3660110” <sip:3660110@199.150.1.1>;tag=199.150.1.1+1+56c....
djacency sip eExampleSIP
nat force-off
method-profile inbound custom-method-profile
method-profile outbound custom-method-profile
error-profile outbound max-call-per-adjacency
hunting-trigger 404 500 503
signaling-address ipv4 199.150.1.1
statistics method summary
signaling-port 5060
remote-address ipv4 166.34.245.231 255.255.255.255
signaling-peer 166.34.245.231
header-name From passthrough
ping-enable
realm outside
attach
Solved! Go to Solution.
01-12-2018 03:30 PM
01-10-2018 10:58 PM
01-11-2018 10:36 AM
Hello Mohammed,
Thank you for response. We are not using dial-peers.
Therefore, I am not able to apply it.
I try to explain the situation:
SIP Client is sending call through SBC to another carrier.
For call identification reasons, we had to apply a customized method profile for this adjacency.
I am wondering, if this could be the cause for the SIP INVITE From Field issue, where instead of the SBC's outside signalling IP, the SIP Server's private IP is passed.
Please see example, the FROM field should contain SBC's Signalling IP and not any information about the
SIP Client Private IP, which is initiating the calls.
Currently:
From: sip:+12125551212@192.168.80.1;tag=887s
Desired:
From: sip:+12125551212@<SBC Outside Signalling IP>;tag=887s
adjacency sip eExample
nat force-off
method-profile inbound custom-method-profile
method-profile outbound custom-method-profile
error-profile outbound max-call-per-adjacency
hunting-trigger 404 500 503
signaling-address ipv4 <SBC Outside Signalling IP>
statistics method summary
signaling-port 5060
remote-address ipv4 <Outside Signalling IP of adjacency peer/Carrier>
signaling-peer <Outside Signalling IP of adjacency peer/Carrier>
header-name From passthrough
ping-enable
realm outside
attach
sip header-profile custom-header-profile
header From entry 1
action as-profile
header X-CardEasy-CID entry 1
action pass
header Remote-Party-ID entry 1
action pass
header P-Asserted-Identity entry 1
action pass
sip method-profile custom-method-profile
method INVITE
action as-profile
header-profile custom-header-profile
01-12-2018 06:14 AM
Could this be because you have this enabled?
"header-name From passthrough"
By default the SBC should include its own IP in the host portion of the From header.
01-12-2018 06:21 AM
01-12-2018 03:30 PM
Correct, removing this parameter fixed it.
Thanks.
01-12-2018 11:29 PM
Glad to hear that but you didn't mark my answer as the resolution. Looks like you marked your post as the solution
01-13-2018 10:47 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide