Hi,
I have fixed this problem. Instead of using a concatenation of callid
and from tag I generate an MD5 string from the two. Please update.
Thanks,
--
Anca Vamanu
www.voice-system.ro
Jeff Pyle wrote:
It seems as though the '@' is causing the Opensips to trip over before a
resulting
It seems as though the '@' is causing the Opensips to trip over before a
resulting packet leaves any local interface:
CRITICAL:core:mk_proxy: could not resolve hostname: 143.95.46.114as5b24544d
ERROR:tm:uri2proxy: bad host name in URI
I started looking at B2BUA top hiding again last night. The from tag on the
outbound side is being built from something (don't remember what) on the
original Invite that contains an @ symbol and domain. Can this be changed? I
am finding quite a few UAs that don't like having that symbol in a
Hi Richard,
Now the from tag is constructed by concatenating the callid and the from
tag of the received Invite. The callid is probably the one containing
'@'. If there are clients that reject this kind of tags, I could take
this character out.
Regards,
--
Anca Vamanu
www.voice-system.ro
Yes please. It's a bit of a problem.
Richard
On Mar 31, 2010, at 1:39 PM, Anca Vamanu wrote:
Hi Richard,
Now the from tag is constructed by concatenating the callid and the from
tag of the received Invite. The callid is probably the one containing
'@'. If there are clients that reject
