Call comes in to one of our DID's, and is forwarded out Level3 (I set
initial ring time to 1, and call to the external destination as
'Always/Enabled, At the same time'
Caller is 561-302-4743, called party is our user 1251 (561-948-2251)
The caller id that shows up at the destination is a '4'. (the first part
of the ITSP account name)
here are results of tests: (yes, I have pcaps, but my Level3 account
number is in there)
I ASSUME Level3 is taking the P-Asserted-Identity and using it as
outbound caller id on forwarded calls, or, if there is a lack of
P-Asserted-Identity, sipx is taking the account name and putting it into
From header. (which Level3 uses as the outbound caller id)
My tests seem to indicate this is the case.
*if this has NOT happened to you, then it is the 'unique*' way Level3
wanted me to set up the ITSP Account part of the gateway
(information in user and password, but we do NOT register on init. we
AUTHENTICATE during the call)
*our setting: Use default asserted identity: Caller ID is '4'*
On INVITE:
tshark -V -r fwd_L3.pcap | grep 1-4K
P-Asserted-Identity: <sip:[email protected]
tshark -V -r fwd_L3.pcap | grep 'From: "sipxbridge"'
From: "sipxbridge"
<sip:[email protected]>;tag=697061275846959940
From: "sipxbridge"
<sip:[email protected]>;tag=697061275846959940
From: "sipxbridge"
<sip:[email protected]>;tag=697061275846959940
From: "sipxbridge"
<sip:[email protected]>;tag=697061275846959940
From: "sipxbridge"
<sip:[email protected]>;tag=697061275846959940
From: "sipxbridge"
<sip:[email protected]>;tag=697061275846959940
From: "sipxbridge"
<sip:[email protected]>;tag=697061275846959940
*Our setting: force P-Asserted-Identity: [email protected]:
Called ID is 5619995000*
tshark -V -r p_assert_5619995000.pcap | grep P-Ass
P-Asserted-Identity: <sip:[email protected]>
tshark -V -r p_assert_5619995000.pcap | grep 'From: "sipxbridge"'
From: "sipxbridge"
<sip:[email protected]>;tag=3477644612316569967
From: "sipxbridge"
<sip:[email protected]>;tag=3477644612316569967
From: "sipxbridge"
<sip:[email protected]>;tag=3477644612316569967
From: "sipxbridge"
<sip:[email protected]>;tag=3477644612316569967
From: "sipxbridge"
<sip:[email protected]>;tag=3477644612316569967
From: "sipxbridge"
<sip:[email protected]>;tag=3477644612316569967
From: "sipxbridge"
<sip:[email protected]>;tag=3477644612316569967
*If I disable P-Asserted-Identity: Called ID '4'*
tshark -V -r p_assert_blank.pcap | grep P-Ass
(nothing)
tshark -V -r p_assert_blank.pcap | grep 1-4
From: "sipxbridge"
<sip:[email protected]>;tag=3505844060207565135
SIP from address: sip:[email protected]
Contact: <sip:[email protected]:5080;transport=udp>
Contact Binding:
<sip:[email protected]:5080;transport=udp>
URI:
<sip:[email protected]:5080;transport=udp>
SIP contact address:
sip:[email protected]:5080
From: "sipxbridge"
<sip:[email protected]>;tag=3505844060207565135
SIP from address: sip:[email protected]
From: "sipxbridge"
<sip:[email protected]>;tag=3505844060207565135
SIP from address: sip:[email protected]
From: "sipxbridge"
<sip:[email protected]>;tag=3505844060207565135
SIP from address: sip:[email protected]
From: "sipxbridge"
<sip:[email protected]>;tag=3505844060207565135
SIP from address: sip:[email protected]
From: "sipxbridge"
<sip:[email protected]>;tag=3505844060207565135
SIP from address: sip:[email protected]
From: "sipxbridge"
<sip:[email protected]>;tag=3505844060207565135
SIP from address: sip:[email protected]
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
