-boun...@list.sipfoundry.orgmailto:sipx-users-boun...@list.sipfoundry.org]
on behalf of Michael Picher [mpic...@ezuce.commailto:mpic...@ezuce.com]
Sent: November 30, 2012 2:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always
of sipXecs software
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always not
available
you'll find you have transfer issues and whatnot with port 5060... it is
not the right port. 5080 is where sipXbridge is listening on. this is not
a typo. the proxy listens on port 5080.
mike
...@list.sipfoundry.org] *On Behalf Of *Nicholas Drayer
*Sent:* Thursday, November 29, 2012 6:11 PM
*To:* Discussion list for users of sipXecs software
*Subject:* Re: [sipx-users] sipx 4.6 inbound ivr--extension always not
available
** **
I put in XX-10547 for the IM-enabled interfering
Nicholas,
This has been on my mind a little over the past few days, was this just a
typo from the 4.4 configuration for ITSP's using 5080 inbound, or is the ITSP
still sending to you on 5080? We tested out inbound on 5060 (albeit weeks ago
and many updates) and it was working fine. I am
you'll find you have transfer issues and whatnot with port 5060... it is
not the right port. 5080 is where sipXbridge is listening on. this is not
a typo. the proxy listens on port 5080.
mike
On Fri, Nov 30, 2012 at 4:21 PM, Trevor L Benson tben...@a-1networks.comwrote:
Nicholas,
This
doh... the proxy listens on 5060
On Fri, Nov 30, 2012 at 5:49 PM, Michael Picher mpic...@ezuce.com wrote:
you'll find you have transfer issues and whatnot with port 5060... it is
not the right port. 5080 is where sipXbridge is listening on. this is not
a typo. the proxy listens on port
Picher
[mpic...@ezuce.com]
Sent: November 30, 2012 2:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always not available
you'll find you have transfer issues and whatnot with port 5060... it is not
the right port. 5080 is where
...@pbx.domain.com:5080.
From: sipx-users-boun...@list.sipfoundry.org
[sipx-users-boun...@list.sipfoundry.org] on behalf of Michael Picher
[mpic...@ezuce.com]
Sent: November 30, 2012 2:49 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipx 4.6 inbound ivr
list for users of sipXecs software
*Subject:* Re: [sipx-users] sipx 4.6 inbound ivr--extension always not
available
The MoH issue is related to Bria: I’ve now figured out that the MoH
issue only occurs happens with the Mac OS X Bria client. Same for the
hold/resume issue – works properly
settings.
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Michael Picher
Sent: November-29-12 2:38 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always not available
fwiw, i
Of Nicholas Drayer
Sent: Thursday, November 29, 2012 6:11 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always not
available
I put in XX-10547 for the IM-enabled interfering with incoming audio
problem. Seems pretty major to me, making
Baclor [jbac...@ezuce.com]
Sent: November 27, 2012 7:26 PM
To: Discussion list for users of sipXecs software
Cc: Nicholas Drayer
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always not available
Check the registration status of the phone in the admin UI. Is it registered?
If so
:* Re: [sipx-users] sipx 4.6 inbound ivr--extension always
not available
Check the registration status of the phone in the admin UI. Is it
registered? If so, is it registered as NATed (sipXnonat tag not
present in contact)? If it is NATED, can you confirm if OPTIONS
keep-alive is received
Baclor [jbac...@ezuce.com]
*Sent:* November 27, 2012 7:26 PM
*To:* Discussion list for users of sipXecs software
*Cc:* Nicholas Drayer
*Subject:* Re: [sipx-users] sipx 4.6 inbound ivr--extension always
not available
Check the registration status of the phone in the admin UI. Is it
registered
]
*Sent:* November 27, 2012 7:26 PM
*To:* Discussion list for users of sipXecs software
*Cc:* Nicholas Drayer
*Subject:* Re: [sipx-users] sipx 4.6 inbound ivr--extension always
not available
Check the registration status of the phone in the admin UI. Is it
registered? If so, is it registered
*Subject:* Re: [sipx-users] sipx 4.6 inbound ivr--extension always not
available
Check the registration status of the phone in the admin UI. Is it
registered? If so, is it registered as NATed (sipXnonat tag not present
in contact)? If it is NATED, can you confirm if OPTIONS keep-alive
Drayer
Cc: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always not available
I was wrong. It's no sipXnonat that you should be looking for but to make sure
your registrations has x-sipX-privcontact. Can you verify this for all your
NATed
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always not available
That all looks good Joegen:
sip:298@x.x.x.x:39212;rinstance=307688e8aaf12fad;transport=tcp;x-sipX-privcontact=10.128.1.32%3A8180%3Btransport%3Dtcp
Pretty much the same from all three sites I'm testing from.
From: Joegen
Drayer
Sent: November-28-12 4:11 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always not available
Another day and yet a bit closer: the Polycom SoundPoint I managed to provision
for this server has no problems whatsoever. MoH, inbound
Subject: Re: [sipx-users] sipx 4.6 inbound ivr--extension always not available
The MoH issue is related to Bria: I’ve now figured out that the MoH issue only
occurs happens with the Mac OS X Bria client. Same for the hold/resume issue –
works properly on Windows, can’t resume on Mac. Both exhibit
Hello,
I've got a test system up, everything works super, except inbound calls: they
do go to the IVR, but when I choose an extension, it is always 'not available'.
I can leave a voice message, and the extension's user can pick retrieve the
voicemail.
I can call out just fine.
I'm using last
Check the registration status of the phone in the admin UI. Is it
registered? If so, is it registered as NATed (sipXnonat tag not
present in contact)? If it is NATED, can you confirm if OPTIONS
keep-alive is received by the phone occasionally if you sniff the
packets from the phones
22 matches
Mail list logo
