I'll try the patch. Thank you for your time.
As for the local and remote media ports :
I have an endpoint with IP xxx.xxx.xxx.xxx and an FS box with IP
yyy.yyy.yyy.yyy.
In a SIP bridge each side of the call leg between the two boxes will
pick a udp port in order to send/receive traffic.
In my CDRs (a-leg) when I call the ${remote_media_port} and
${local_media_port} it returns the same value (e.g. 18841) for both
endpoints
(yyy.yyy.yyy.yyy and xxx.xxx.xxx.xxx).
In my b-leg CDR (let's say yyy.yyy.yyy.yyy to zzz.zzz.zzz.zzz) both
variables hold the same value as well but a different
one than the a-leg's (e.g. 19871)
The way I thought it would happen is that each call leg would have a
pair of different port numbers for the two variables
because :
yyy would inform xxx that it should use port A
xxx would inform yyy that it should use port B
(that's one pair)
yyy would inform zzz that it should use port C
zzz would inform yyy that it should use port D
(that's another pair)
so for the a-leg : ${local_media_port} = A, ${remote_media_port} = B
for the b=leg : ${local_media_port} = C, ${remote_media_port} = D
Am I missing something?
Anthony Minessale wrote:
> It's not an unreasonabe request so i added a patch you can test for me
> to trunk that sets network_addr on the reciept of a reply to an invite
> on an outbound call. and the 2 variables sip_reply_host and sip_reply_port
>
>
>
>
> local and remote media port reflects the port being used between that
> leg and it's remote connection eg the ip and port that the rtp stack
> was asked to use.
>
>
> On Wed, Dec 3, 2008 at 9:48 AM, [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
> wrote:
>
> 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, [EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]>> 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, [EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]> <[EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]>> 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
>>> [email protected]
>>> <mailto:[email protected]>
>>> 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:[EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]>
>>> GTALK/JABBER/PAYPAL:[EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]>
>>> IRC: irc.freenode.net <http://irc.freenode.net> #freeswitch
>>>
>>> FreeSWITCH Developer Conference
>>> sip:[EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]>
>>> iax:[EMAIL PROTECTED]/888
>>> <http://iax:[EMAIL PROTECTED]/888>
>>> googletalk:[EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]>
>>> pstn:213-799-1400
>>>
>>> ------------------------------------------------------------------------
>>> _______________________________________________
>>> Freeswitch-users mailing list
>>> [email protected]
>>> <mailto:[email protected]>
>>> 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
>> [email protected]
>> <mailto:[email protected]>
>> 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:[EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]>
>> GTALK/JABBER/PAYPAL:[EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]>
>> IRC: irc.freenode.net <http://irc.freenode.net> #freeswitch
>>
>> FreeSWITCH Developer Conference
>> sip:[EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]>
>> iax:[EMAIL PROTECTED]/888
>> <http://iax:[EMAIL PROTECTED]/888>
>> googletalk:[EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]>
>> pstn:213-799-1400
>> ------------------------------------------------------------------------
>> _______________________________________________ Freeswitch-users
>> mailing list [email protected]
>> <mailto:[email protected]>
>> 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
> [email protected]
> <mailto:[email protected]>
> 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:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> GTALK/JABBER/PAYPAL:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> IRC: irc.freenode.net <http://irc.freenode.net> #freeswitch
>
> FreeSWITCH Developer Conference
> sip:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> iax:[EMAIL PROTECTED]/888
> <http://iax:[EMAIL PROTECTED]/888>
> googletalk:[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
> pstn:213-799-1400
> ------------------------------------------------------------------------
>
> _______________________________________________
> Freeswitch-users mailing list
> [email protected]
> 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
[email protected]
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
