Search found 71 matches

by fe80
22 Aug 2019 07:58
Forum: H323 / IP / Pimphony
Topic: NOT RECEIVING INCOMING PRIVATE SIP NUMBERS ON OXO
Replies: 6
Views: 634

Re: NOT RECEIVING INCOMING PRIVATE SIP NUMBERS ON OXO

<code>Reason: Q.805;text=" Incoming calls barred within CUG";cause=55</code> points normally to a barring problem.
by fe80
22 Aug 2019 07:52
Forum: H323 / IP / Pimphony
Topic: Polycom SIP won't register on OXO R9.2
Replies: 4
Views: 456

Re: Polycom SIP won't register on OXO R9.2

standard port for sip phones is 5059
by fe80
08 Jan 2019 05:15
Forum: H323 / IP / Pimphony
Topic: Analog Modem over SIP
Replies: 9
Views: 3322

Re: Analog Modem over SIP

I can't believe this because OXOs DSP is unable to encode G.722
by fe80
27 Jul 2018 04:28
Forum: Configuration
Topic: STOP CALL PROCEEDING MESSAGE ISDN TO FOR PATTON SIP IAD
Replies: 1
Views: 1107

Re: STOP CALL PROCEEDING MESSAGE ISDN TO FOR PATTON SIP IAD

I would play with PRACK and P-EARLY-MEDIA settings of the Patton box or would use a recent OXO software and let OXO speak SIP directly with Broadworks
by fe80
27 Jul 2018 04:13
Forum: SIP
Topic: Do not display name in SIP-herder
Replies: 17
Views: 3850

Re: Do not display name in SIP-herder

Okay, thank you clarifying this. In this case OXO is more flexible. Just flipping SIPOgDspNm switch to "false" and you're done.. ;)
by fe80
26 Jul 2018 04:53
Forum: SIP
Topic: Do not display name in SIP-herder
Replies: 17
Views: 3850

Re: Do not display name in SIP-herder

Hi,

A workaround is to disable CLIR/RFC3325 but this is needed for privacy outgoing calls.
What was the solution for this without disable CLIR/RFC3325?

I dont want:
From: "real name" <sip:1234@xxx.yyy>

instead I need:
From: <sip:1234@xxx.yyy>

for outgoing calls through ext sip gw (on Rel 12.1)
by fe80
12 Jan 2018 03:42
Forum: MAIN
Topic: DTMF not working when dialing certain numbers
Replies: 6
Views: 1950

Re: DTMF not working when dialing certain numbers

Is RTP_DIRECT=true? In this case you will not see RTP on WebDiag traces while IP phones are used for the call. You need to take the trace from your access router.
by fe80
12 Jan 2018 03:35
Forum: H323 / IP / Pimphony
Topic: PIMphony updates secure channel failure
Replies: 2
Views: 1947

Re: PIMphony updates secure channel failure

Yes. Its caused by a cipher suite mismatch between PIMphony and OXO. Turning off HTTPS is a temporary solution.
by fe80
12 Jan 2018 03:28
Forum: Applications
Topic: ACD OXO Agent Assistant can not make calls on Windows 7-10
Replies: 2
Views: 1543

Re: ACD OXO Agent Assistant can not make calls on Windows 7-10

Please try to change the following registry settings in your windows client:

Code: Select all

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319
"SystemDefaultTlsVersions"=dword:00000001

Go to advanced search