Displaying 2 results from an estimated 2 matches for "call_source_e164".
2003 Jul 16
3
Segmentation fault with chan_oh323
...ine 1529 (copy_call_details): call_source_alias = tnt [192.168.0.227]
Jul 16 18:33:12 DEBUG[196621]: File chan_oh323.c, Line 1530 (copy_call_details): call_dest_alias = 12125551234 12125551234 ip$192.168.0.70:1720
Jul 16 18:33:12 DEBUG[196621]: File chan_oh323.c, Line 1531 (copy_call_details): call_source_e164 = phone number
Jul 16 18:33:12 DEBUG[196621]: File chan_oh323.c, Line 1532 (copy_call_details): call_dest_e164 = 12125551234
That's it. And gatekeeper log shows that after normal ARQ-ACF exchange originating device
immediately sent DRQ.
If anybody knows a reason for this (and the way to fix it...
2004 Dec 13
0
[oh323] sporadic call setup
..., 9205,0721*8 []'
Dec 13 13:13:05 DEBUG[-1275274320]: chan_oh323.c:2681 copy_call_details: call_dest_alias = '2005 '
Dec 13 13:13:05 DEBUG[-1275274320]: chan_oh323.c:2682 copy_call_details: call_source_e164 = '8900'
Dec 13 13:13:05 DEBUG[-1275274320]: chan_oh323.c:2683 copy_call_details: call_dest_e164 = '2005'
Dec 13 13:13:05 DEBUG[-1275274320]: chan_oh323.c:2684 copy_call_details: remote_app = ' 118.67/30593'
Dec 13 13:13:05 DEBUG[-1275274320]: chan_oh323.c:2685 copy_...