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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

8440 Spectrlink

Status
Not open for further replies.

mojoputter

Technical User
Oct 11, 2005
1,123
US
We have about 15 Spectralink 8440's newly installed on a 9.1 server edition, we've gone through every Avaya/Spectralink document and got them working internally just fine. But we can't call out on the 8440's, after looking at a call in Monitor there's a few questions I have as far as whats being displayed. The Unallocated (unassigned) number and the TARGET: Not in dial plan, is this as a result of the T1 vendor denying the call..?

585340349mS SIP Call Tx: phone
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.7.0.117;branch=z9hG4bK32198d9a95C22C1B
From: "matrix test wifi" <sip:5998@10.7.1.80>;tag=C6C15D44-503D012D
Call-ID: f8da80-6ae8b3d9-e44e3d76@10.7.0.117
CSeq: 1 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,SUBSCRIBE,REGISTER,PUBLISH,UPDATE
Supported: timer,100rel
Server: IP Office 9.1.6.0 build 153
Reason: Q.850;cause=1;text="Unallocated (unassigned) number"
To: <sip:97634755595@10.7.1.80;user=phone>;tag=fe75954ca844a9f7
Content-Length: 0




0a07015000003152 351.12626.0 3622 Matrixx.0: LOOKUP CALL ROUTE: GID=0 type=100 called_party=97634755595 sub= calling=5998 calling_sub= dir=out complete=1 ses=0
0a07015000003152 351.12626.0 3622 Matrixx.0: ADD TARGET (N): number=97634755595 type=100 depth=1 nobar=1 setorig=1 ses=0
0a07015000003152 351.12626.0 3622 Matrixx.0: TARGET: Not in dial plan


 
In all SIP registration fiels of the user in Spectralink enter the phone number then you should see this:
From: 5998 <sip:5998@10.7.1.80>;tag=C6C15D44-503D012D
instead of this:
From: "matrix test wifi" <sip:5998@10.7.1.80>;tag=C6C15D44-503D012D

test again after changing the parameters.
 
We did make the change you suggested and that did help. We got it not to give us an error tone now but still not able to go out of the system, it appears to be getting stuck in the ARS table.
In system Status its current state says "Waiting for Line" and in the monitor screen that it can't find GROUP ID 1 which is the T1 group.
Going to tweek the ARS table a little


512905794mS CMARS: FORM: Main - Received Number: 7631211234@10.8.1.70
512905795mS CMARS: FOUND A SHORT CODE - short_code: N; - Tel: N - Called_Party: 7631211234@10.8.1.70 - Line Group Id: 1
512905795mS CMARS: SetCurrentTarget: Short_Code: N; - Line_Group_ID: 1
512905795mS CMARS: FindActiveARSByGroupID GroupID=1 - Not Found
512905795mS CMLRQ: FindActiveLRQByGroupID GroupID=1 - Not Found
512905795mS CMCallEvt: 0000000000000000 0.22816.0 -1 BaseEP: NEW CMEndpoint f160c684 TOTAL NOW=25 CALL_LIST=10
512905796mS CMTARGET: ISDN BChannel 21: in-service check = 1
512905796mS CMTARGET: ISDN BChannel 21: in-service check = 1
512905797mS CMARS: ModifyCMARSTarget: Short_Code: N; - Line_Group_ID: 1 set line status to CMARS_TRYING
512905798mS CMARS: FOUND LINE - Line Id: 14 - using line group id: 1 (code N;, line 1) - Called Number: 7631211234@10.8.1.70 - Calling Number: 5158
512905798mS CMARS: SEND Setup TO LINE
512905798mS CMCallEvt: 0a07015100005920 0.22816.0 7000 Q931 Trunk:14 CHAN=21: StateChange: END=child CMCSIdle->CMCSOffering
 
But it finds the line group as trunk instead of ARS.

FOUND LINE - Line Id: 14 - using line group id: 1 (code N;, line 1) - C

Where does the @IPAddress come from?
 
One of the other techs found something on Tek Tips that says to add a SC to the user(5158)
SC 9N
TN N"@10.8.1.70"
Feat Dial
LN Grp 50:Main

if that's not in there then the call goes no where
 
Actually it was our friend Intrigrant that posted that SC 3 years ago, maybe its not valid for 9.1
 
Haha, times are a changing my friend.
Indeed, since R7 the "@IP Address" can be left out as it will be automaticly populated from the SIP trunk, something Avaya should have done from day one.
 
Even if it is R6... The @ part is not needed on ISDN lines...
 
Intrigrant were not using SIP trunks and I also see now that on the system tab we have SIP trunks enable, could be part of the issue.
Unfortunately to change that and test would mean a reboot

Capture_vlaeg7.png



This was also in the monitor, googling 404 Not Found, something is F-ed up

521651446mS SIP Call Tx: phone
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.8.0.180;branch=z9hG4bK84d917d24DA0EAA
From: "5158" <sip:5158@10.8.1.70>;tag=A1DDE257-B17E23FC
Call-ID: a3db1f13-dd49fb08-8d68c099@10.8.0.180
CSeq: 1 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,NOTIFY,SUBSCRIBE,REGISTER,PUBLISH,UPDATE
Supported: timer,100rel
Server: IP Office 9.1.6.0 build 153
Reason: Q.850;cause=1;text="Unallocated (unassigned) number"
To: <sip:97631211234@10.8.1.70;user=phone>;tag=308f7a4cdd1eeac3
Content-Length: 0
 
Reason: Q.850;cause=1;text="Unallocated (unassigned) number"

This means that the dialled number is not recognized by IP Office as a valid number

As the number is not in the trace I assume you check your shortcodes in user, system and ARS to see if there is a match or not.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top