OXO--Open Touch connection
OXO--Open Touch connection
Hi everyone I have a problem concerning the interconnection between OmniPCX Office 9.1 and opentouch 1. They are connected using sip trunk. User A is located in OXO and B in open touch. The algorithm used id G711. When A calls B, the communication is ok. When B calls A the set rings ok when they try to answer the communication is cut (on off hook). On the sip trace I get
SIP/2.0 488 Not Acceptable Here
User-Agent: OXO_GW_910/037.001
Reason: Q.850;text="Bearer capability not implemented";cause=65
Warning: 305 172.16.9.11 "No Common Codec"
To: <sip:1605@172.16.9.11;user=phone>;tag=156c519c15a5a4cc7d09114beede8b27
From: "Visitor ." <sip:97976301@172.16.29.3;user=phone>;tag=c38a3dd4cb04685cfec6c898feed4edf
Call-ID: ea8ba72963b17daf14b9765b6b602946@172.16.29.3
CSeq: 322437136 INVITE
Via: SIP/2.0/UDP 172.16.29.3;branch=z9hG4bKea6776f855cb7a64fbdd911c28438b8a
Content-Length: 0
SIP/2.0 488 Not Acceptable Here
User-Agent: OXO_GW_910/037.001
Reason: Q.850;text="Bearer capability not implemented";cause=65
Warning: 305 172.16.9.11 "No Common Codec"
To: <sip:1605@172.16.9.11;user=phone>;tag=156c519c15a5a4cc7d09114beede8b27
From: "Visitor ." <sip:97976301@172.16.29.3;user=phone>;tag=c38a3dd4cb04685cfec6c898feed4edf
Call-ID: ea8ba72963b17daf14b9765b6b602946@172.16.29.3
CSeq: 322437136 INVITE
Via: SIP/2.0/UDP 172.16.29.3;branch=z9hG4bKea6776f855cb7a64fbdd911c28438b8a
Content-Length: 0
- tot3nkopf
- Alcatel Unleashed Certified Guru
- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: OXO--Open Touch connection
Code: Select all
Warning: 305 172.16.9.11 "No Common Codec"
Re: OXO--Open Touch connection
thanks for the reply
yes it is !but how do i solve it? both pbx have the same codec. so what is the problem?
yes it is !but how do i solve it? both pbx have the same codec. so what is the problem?
- tot3nkopf
- Alcatel Unleashed Certified Guru
- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: OXO--Open Touch connection
framing?mgsox wrote:thanks for the reply
yes it is !but how do i solve it? both pbx have the same codec. so what is the problem?
Re: OXO--Open Touch connection
the codec is g711 a-law 20ms ( i should have said that before! sorry) the connection was working when oxo was r8. we have upgraded the system few days a go
- tot3nkopf
- Alcatel Unleashed Certified Guru
- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: OXO--Open Touch connection
if you leave default on OXO side what happens?mgsox wrote:the codec is g711 a-law 20ms ( i should have said that before! sorry) the connection was working when oxo was r8. we have upgraded the system few days a go
Re: OXO--Open Touch connection
we have the same issue. that is why we only configured one type of code in both sites to see if there was a mismatch. ( a new codec g722 is on the market!)
- tot3nkopf
- Alcatel Unleashed Certified Guru
- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
Re: OXO--Open Touch connection
Check codec pass-through settings on OXO side.mgsox wrote:the codec is g711 a-law 20ms ( i should have said that before! sorry) the connection was working when oxo was r8. we have upgraded the system few days a go
If you dial from an analog or digital set you have the same issue?
- cavagnaro
- Alcatel Unleashed Certified Guru
- Posts: 7014
- Joined: 14 Sep 2005 19:45
- Location: Brasil, Porto Alegre
- Contact:
Re: OXO--Open Touch connection
I don't believe it... check the negotiation messages and verify codec is the same. Avoid multicoding
Sent from my XPeria Z
Sent from my XPeria Z
Ignorance is not the problem, the problem is the one who doesn't want to learn
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
Re: OXO--Open Touch connection
Case solved!
If I configure the ars of oxo to have default compression, it works fine.
It looks like a bug to me but is a work around!
Thank you all for your help
If I configure the ars of oxo to have default compression, it works fine.
It looks like a bug to me but is a work around!
Thank you all for your help