I looked in the b-leg xml cdr and the ip address is not there (for signaling) it is only there
for media (${remote_media_ip}) which is not the same thing now, is it?
While we are at it, I noticed that the ${local_media_port} and ${remote_media_port}
have the same value for each CDR (a or b leg). Shouldn't the first variable hold the port
of the FS (on both legs) and the second variable the port of the client (in the a-leg) or the port of
the provider (in the b-leg)?
Anthony Minessale wrote:outgoing calls to not have an ip value set.
if you want to store the dest ip in the cdr you need to set it as a custom variable and insert it
into your template for csv cdr or it will just be there in xml cdr
On Wed, Dec 3, 2008 at 8:18 AM, regs@kinetix.gr <regs@kinetix.gr> wrote:
b-leg logging is enabled in the cdr module. but in the cdrs I cannot get any variables that refer to the b-leg.
I tried the second way using ${sip_to_host} and {bleg_sip_to_host} but :
a) the variable returns the FS IP on the a-leg CDR (correctly)
b) the variable returns nothing on the b-leg CDR (empty). Shouldn't it return the "to" host of the b-leg (my providers address)?
Anthony Minessale wrote:2 options.
1) enable b-leg logging on the cdr module.
2) you can use the prefix bleg_ in a variable context to get to caller_profile members
from the b leg.
eg ${bleg_caller_id_name}
On Wed, Dec 3, 2008 at 7:30 AM, regs@kinetix.gr <regs@kinetix.gr> wrote:
Hi,
I am making a simple bridge between two call legs :
Client --(a-leg)--> FS --(b-leg)-->Provider
How can I get information like network-address of the Provider,
media-address,
port used, media port used etc. from the second leg (b-leg)?
Is all the information provided by the a-leg available for the b-leg as
well? If, yese
how can I access it? (and log it to my CDR file eventually)
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
--
Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
--
Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org