[Freeswitch-users] Out of band Signaling (RFC2833) getting lost between legs

Örn Arnarson orn at arnarson.net
Wed Jul 16 14:06:08 MSD 2014


If that were the case, shouldn't FS not send any RFC2833 to the other leg
at all, rather than randomly selecting an elite few?

In any case, it seems to me that the negotiation agrees upon rfc2833
(src/dst summary in bold):

*From: 10.171.32.32 To: 10.10.10.10 SIP/SDP Request: INVITE
sip:5821000 at 10.10.10.10 <sip%3A5821000 at 10.10.10.10>, with session
description*
INVITE sip:5821000 at 10.10.10.10 SIP/2.0
f: 4151664 <sip:4151664 at 10.10.10.10:5060>;tag=1917942741
 t: <sip:5821000 at 10.10.10.10>
i: 350118871 at 10.171.32.32
CSeq: 21 INVITE
v: SIP/2.0/UDP 10.171.32.32:5060;branch=z9hG4bK846121329
m: <sip:4151664 at 10.171.32.32:5060>
Proxy-Authorization: Digest username="4151664", realm="10.10.10.10",
nonce="3e7ec346-0c38-11e4-8a0e-33b1e8545015", uri="sip:5821000 at 10.10.10.10",
response="ffca158008f6fd4a0939f50d644fd328", algorithm=MD5,
cnonce="0a4f113b", qop=auth, nc=00000001
c: application/sdp
Allow: NOTIFY,REFER,INVITE,ACK,CANCEL,BYE,UPDATE,OPTIONS
Max-Forwards: 70
User-Agent: Telsey UA
K: replaces,100rel,update,options
Expires: 180
Content-Length:   316

v=0
o=TelseySIP 441685930 441685930 IN IP4 10.171.32.32
s=SIP Call
c=IN IP4 10.171.32.32
t=0 0
m=audio 4002 RTP/AVP 8 0 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=fmtp:18 annexb=no
a=ptime:20
a=silenceSupp:off
a=sendrecv

*From: 192.168.48.52 To: 192.168.129.7 SIP/SDP Request: INVITE
sip:5821000 at 192.168.129.7 <sip%3A5821000 at 192.168.129.7>, with session
description*
 INVITE sip:5821000 at 192.168.129.7 SIP/2.0
Via: SIP/2.0/UDP 192.168.48.52:5080;rport;branch=z9hG4bKUyD5yU8e4a6HD
Max-Forwards: 69
From: "4151664" <sip:4151664 at 192.168.48.52>;tag=mXc0vQZry6a0a
To: <sip:5821000 at 192.168.129.7>
Call-ID: 15e59578-86db-1232-4382-0000b2133034
CSeq: 62383757 INVITE
Contact: <sip:mod_sofia at 192.168.48.52:5080>
User-Agent:
FreeSWITCH-mod_sofia/1.2.0-rc2+git~20120626T232126Z~909fca199d+unclean~20120627T115626Z
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER,
REFER, NOTIFY
Supported: timer, precondition, path, replaces
Allow-Events: talk, hold, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 294
X-FS-Support: update_display,send_info
Remote-Party-ID: "4151664" <sip:4151664 at 192.168.48.52
>;party=calling;screen=yes;privacy=off

v=0
o=FreeSWITCH 1405420725 1405420726 IN IP4 192.168.48.52
s=FreeSWITCH
c=IN IP4 192.168.48.52
t=0 0
m=audio 18918 RTP/AVP 8 0 18 101 13
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20

*From: 192.168.129.7 To: 192.168.48.52 SIP/SDP Status: 200 OK, with session
description*
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.48.52:5080
;received=192.168.48.52;rport=5080;branch=z9hG4bKUyD5yU8e4a6HD
Record-Route: <sip:192.168.129.7;lr;ftag=mXc0vQZry6a0a;did=a96.b25ba4e7>
From: "4151664" <sip:4151664 at 192.168.48.52>;tag=mXc0vQZry6a0a
To: <sip:5821000 at 192.168.129.7>;tag=Q4ra7Z32aUaQQ
Call-ID: 15e59578-86db-1232-4382-0000b2133034
CSeq: 62383757 INVITE
Contact: <sip:5821000 at 172.25.200.121:5080;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.2.7
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, precondition, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 267
X-FS-Display-Name: Outbound Call
X-FS-Display-Number: sip:5821000 at 192.168.129.7
 X-FS-Support: update_display,send_info
Remote-Party-ID: "Outbound Call" <sip:5821000 at 192.168.129.7
>;party=calling;privacy=off;screen=no

v=0
o=FreeSWITCH 1405409349 1405409350 IN IP4 192.168.129.7
s=FreeSWITCH
c=IN IP4 192.168.129.7
t=0 0
m=audio 51836 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=nortpproxy:yes

*From: 10.10.10.10 To: 10.171.32.32 SIP/SDP Status: 200 OK, with session
description*
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.48.52:5080
;received=192.168.48.52;rport=5080;branch=z9hG4bKUyD5yU8e4a6HD
Record-Route: <sip:192.168.129.7;lr;ftag=mXc0vQZry6a0a;did=a96.b25ba4e7>
From: "4151664" <sip:4151664 at 192.168.48.52>;tag=mXc0vQZry6a0a
To: <sip:5821000 at 192.168.129.7>;tag=Q4ra7Z32aUaQQ
Call-ID: 15e59578-86db-1232-4382-0000b2133034
CSeq: 62383757 INVITE
Contact: <sip:5821000 at 172.25.200.121:5080;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.2.7
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, precondition, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 267
X-FS-Display-Name: Outbound Call
X-FS-Display-Number: sip:5821000 at 192.168.129.7
 X-FS-Support: update_display,send_info
Remote-Party-ID: "Outbound Call" <sip:5821000 at 192.168.129.7
>;party=calling;privacy=off;screen=no

v=0
o=FreeSWITCH 1405409349 1405409350 IN IP4 192.168.129.7
s=FreeSWITCH
c=IN IP4 192.168.129.7
t=0 0
m=audio 51836 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=nortpproxy:yes

=================

Is there anything I'm missing? Is there some obvious error in the original
INVITE or something?

Regards,
Örn





On Tue, Jul 15, 2014 at 5:18 PM, Brian West <brian at freeswitch.org> wrote:

> I'm going to suspect based on your description that one leg didn't
> negotiate rfc2833 (i.e. telephony-event wasn't in the 200 OK back to us),
> in which case it would be improper for us to blindly send rfc2833 down that
> link.
>
> Never fear, the head pounding pain of interop is here to save your day:
>
>
> https://wiki.freeswitch.org/wiki/Behavior_Impacting_Changes_History
>
>
>
> On Tue, Jul 15, 2014 at 11:11 AM, Örn Arnarson <orn at arnarson.net> wrote:
>
>> Thanks!
>>
>> Unfortunately though, it doesn't seem to work. I've both tried setting
>> the variable and exporting it. I'm still seeing an output vastly different
>> from the input, for some reason. As can be seen below, only some digits get
>> sent to 192.168.129.7.
>>
>> FreeSWITCH has the IPs 10.10.10.10 and 192.168.48.52.
>>
>> No.     Time        Source                Destination           Protocol
>> Info
>>     828 4.608522    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     833 4.628531    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     836 4.648536    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     839 4.668542    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     843 4.698593    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1 (end)
>>     844 4.708534    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1 (end)
>>     846 4.718541    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1 (end)
>>     898 4.988589    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Five 5
>>     901 4.990982    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Five 5
>>     902 5.008538    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Five 5
>>     905 5.011005    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Five 5
>>     906 5.028518    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Five 5
>>     909 5.031002    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Five 5
>>     910 5.048645    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Five 5
>>     913 5.050972    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Five 5
>>     916 5.078489    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Five 5 (end)
>>     917 5.088538    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Five 5 (end)
>>     920 5.091026    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Five 5 (end)
>>     921 5.098530    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Five 5 (end)
>>     924 5.111009    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Five 5 (end)
>>     927 5.131108    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Five 5 (end)
>>     977 5.488529    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1
>>     978 5.490940    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     979 5.508533    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     980 5.510907    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     981 5.528496    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     982 5.530959    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     983 5.548501    10.171.32.32          10.10.10.10           RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     984 5.550951    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF One 1
>>     985 5.578513    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1 (end)
>>     986 5.588513    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1 (end)
>>     987 5.590943    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF One 1 (end)
>>     988 5.598495    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1 (end)
>>     989 5.610927    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF One 1 (end)
>>     990 5.630943    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF One 1 (end)
>>    1024 5.968517    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Two 2
>>    1025 5.970978    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Two 2
>>    1026 5.988490    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Two 2
>>    1027 5.991013    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Two 2
>>    1028 6.008497    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Two 2
>>    1029 6.010947    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Two 2
>>    1031 6.028535    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Two 2
>>    1032 6.030954    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Two 2
>>    1033 6.058529    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Two 2 (end)
>>    1034 6.068485    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Two 2 (end)
>>    1035 6.070919    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Two 2 (end)
>>    1036 6.078533    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Two 2 (end)
>>    1037 6.090954    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Two 2 (end)
>>    1038 6.110933    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Two 2 (end)
>>    1082 6.548516    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8
>>    1083 6.551101    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Eight 8
>>    1084 6.568511    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8
>>    1085 6.571134    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Eight 8
>>    1086 6.588535    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8
>>    1087 6.591116    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Eight 8
>>    1088 6.608514    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8
>>    1089 6.610927    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Eight 8
>>    1090 6.639282    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8 (end)
>>    1091 6.648577    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8 (end)
>>    1092 6.650946    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Eight 8 (end)
>>    1093 6.658495    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8 (end)
>>    1094 6.670941    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Eight 8 (end)
>>    1095 6.690934    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Eight 8 (end)
>>    1124 6.968535    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3
>>    1125 6.970995    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Three 3
>>    1126 6.988549    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3
>>    1127 6.991031    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Three 3
>>    1128 7.008525    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3
>>    1129 7.011007    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Three 3
>>    1130 7.028528    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3
>>    1131 7.030982    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Three 3
>>    1132 7.069326    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3 (end)
>>    1133 7.071003    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Three 3 (end)
>>    1134 7.078483    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3 (end)
>>    1135 7.088488    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3 (end)
>>    1136 7.090986    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Three 3 (end)
>>    1137 7.110955    192.168.48.52          192.168.129.7         RTP
>> EVENT Payload type=RTP Event, DTMF Three 3 (end)
>>    1169 7.428561    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3
>>    1171 7.448498    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3
>>    1173 7.468582    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3
>>    1174 7.488494    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3
>>    1175 7.528524    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3 (end)
>>    1176 7.538541    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3 (end)
>>    1177 7.548477    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Three 3 (end)
>>    1210 7.908558    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8
>>    1212 7.928502    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8
>>    1213 7.948499    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8
>>    1214 7.968503    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8
>>    1215 8.008519    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8 (end)
>>    1216 8.018475    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8 (end)
>>    1217 8.028492    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Eight 8 (end)
>>    1256 8.448581    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1
>>    1258 8.468498    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1
>>    1259 8.488576    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1
>>    1260 8.508518    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1
>>    1261 8.549017    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1 (end)
>>    1262 8.558481    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1 (end)
>>    1263 8.568565    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF One 1 (end)
>>    1299 8.928580    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Nine 9
>>    1301 8.948552    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Nine 9
>>    1302 8.968501    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Nine 9
>>    1303 8.988530    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Nine 9
>>    1304 9.028505    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Nine 9 (end)
>>    1305 9.038490    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Nine 9 (end)
>>    1306 9.048479    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Nine 9 (end)
>>    1333 9.348515    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Pound #
>>    1335 9.368529    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Pound #
>>    1336 9.388527    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Pound #
>>    1337 9.408512    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Pound #
>>    1338 9.438487    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Pound # (end)
>>    1340 9.448535    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Pound # (end)
>>    1342 9.458493    10.171.32.32          10.10.10.10           RTP EVENT
>> Payload type=RTP Event, DTMF Pound # (end)
>>
>> Any other ideas?
>>
>> Regards,
>> Örn
>>
>>
>> On Tue, Jul 15, 2014 at 1:37 PM, Kristian Kielhofner <kris at kriskinc.com>
>> wrote:
>>
>>> https://wiki.freeswitch.org/wiki/Variable_pass_rfc2833
>>>
>>> On Tue, Jul 15, 2014 at 7:39 AM, Örn Arnarson <orn at arnarson.net> wrote:
>>> > Hello,
>>> >
>>> > I have an inbound call to FS with RFC2833 signaling. FreeSWITCH
>>> bridges the
>>> > call to another profile. A pcap shows a certain DTMF sequence on the
>>> inbound
>>> > leg, and another on the outbound leg. The sequence on the outbound leg
>>> is
>>> > missing some digits from the sequence. Seemingly at random -- I can
>>> generate
>>> > the same sequence twice and a different sequence will be put through.
>>> The
>>> > interval between the digits does not seem to matter either.
>>> >
>>> > Firstly, has anyone ever heard of something similar?
>>> > Secondly, I was informed by someone on #freeswitch on freenode that FS
>>> > actually regenerates the signaling on the second leg. Can I make FS
>>> just
>>> > blindly forward the RTP events instead of regenerating them to avoid
>>> this
>>> > problem?
>>> >
>>> > Regards,
>>> > Örn
>>> >
>>> >
>>> _________________________________________________________________________
>>> > Professional FreeSWITCH Consulting Services:
>>> > consulting at freeswitch.org
>>> > http://www.freeswitchsolutions.com
>>> >
>>> > 
>>> > 
>>> >
>>> > Official FreeSWITCH Sites
>>> > http://www.freeswitch.org
>>> > http://wiki.freeswitch.org
>>> > http://www.cluecon.com
>>> >
>>> > FreeSWITCH-users mailing list
>>> > FreeSWITCH-users at lists.freeswitch.org
>>> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>> > UNSUBSCRIBE:
>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>> > http://www.freeswitch.org
>>> >
>>>
>>>
>>>
>>> --
>>> Kristian Kielhofner
>>>
>>> _________________________________________________________________________
>>> Professional FreeSWITCH Consulting Services:
>>> consulting at freeswitch.org
>>> http://www.freeswitchsolutions.com
>>>
>>> 
>>> 
>>>
>>> Official FreeSWITCH Sites
>>> http://www.freeswitch.org
>>> http://wiki.freeswitch.org
>>> http://www.cluecon.com
>>>
>>> FreeSWITCH-users mailing list
>>> FreeSWITCH-users at lists.freeswitch.org
>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>>> http://www.freeswitch.org
>>>
>>
>>
>> _________________________________________________________________________
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> http://www.freeswitchsolutions.com
>>
>> 
>> 
>>
>> Official FreeSWITCH Sites
>> http://www.freeswitch.org
>> http://wiki.freeswitch.org
>> http://www.cluecon.com
>>
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>>
>>
>
>
> --
>
> *Brian West*
> brian at freeswitch.org
>
>
> *Twitter: @FreeSWITCH , @briankwest*
> http://www.freeswitchbook.com
> http://www.freeswitchcookbook.com
>
> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378)
> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> 
> 
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20140716/44f2bb46/attachment-0001.html 


Join us at ClueCon 2016 Aug 8-12, 2016
More information about the FreeSWITCH-users mailing list