Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

3rd party sip endpoint help

Status
Not open for further replies.

montyzummer

IS-IT--Management
Oct 6, 2010
2,999
GB
Hi all,

I have a 3rd party endpoint that i can create as a H323 endpoint fine and it registers no problems, then when i create a Sip extn and try to register the endpoint i get the following attached messages in the monitor , the 3rd party endpoint is capable of SIP connectivity, and bypassing the ipo and doing a point to point connection accross the net,
both protocols are fine , why use sip if H323 works i hear you ask?, well you know customers and that is what they are asking for, ultimatly the customer wants 5 of these enpoints in a HG queuing calls, any thoughts would help , i have played with all settings i can think of , IPO is on 7.05.
Thanks in advance.

APSS (SME)
ACSS (SME)
 
Looks like you are trying to log it in as 302 which is a non IP(Dig or analogue) device, so it's not allowing it :)

NTE-wave-logo-for-a4-header.jpg
 
110808736mS H323Evt: RRQ --- Cannot create an extension(vcon2 302) or the extension number is allocated to a non-IP extn

Kyle Holladay / IPOfficeHelp.com
ACSS & APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
Delete the user in the Manager.
Make sure you have the option Auto-create user ticke on LAN1 or 2.

Change the password on the SIP extension into 1234 it should auto create the user in the IPO. For Auth name use the extension number not the

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
name.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
ok will try that cheers.and let you know,

Cheers guys.


APSS (SME)
ACSS (SME)
 
also i had noticed the non ip extnmarker but have ticked the reserve third party endpoint in the extension tab in extn 302, just thought that may help.

Regards

APSS (SME)
ACSS (SME)
 
Bas tried what you said removed the user, didnt work so then i removed the user and extn , created a new extn reserved a 3rd party enpoint on the lan 1 tab, checked auto create user but that will not let me tick that field unless auto create extn is ticked also , also on the sip register tab, checked auto create tab , as the one under the voip tab in lan 1 is for H323 , monitor still throws out the same message: 110808736mS H323Evt: RRQ --- Cannot create an extension(307) or the extension number is allocated to a non-IP extn , i created a different extn number 307 just to see if that was causing an issue.

Any more ideas.

APSS (SME)
ACSS (SME)
 
>110808736mS H323Evt: RRQ --- Cannot create an extension(307)

Is it possible that the endpoint is trying to register as H323?

Wireshark trace may help

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
I take your point but why would it do that , it does register as H323 fine and in the endpoint you can change the protocol to sip and then get the sip traces in monitor but good point and i will give it a go i just dont understand why it would try and register as H323 but stranger things have happened.

APSS (SME)
ACSS (SME)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top