Topic: Polycom Ver 3.2.3.1734 [Comments: 2]
moshe

Fri, 04/30/2010 - 08:24 | Polycom Ver 3.2.3.1734

i upgrade polycom firmware version 3.2.3.1734 and a strange issue started

when a call hits a hunt list device base ring group some extensions in the group are not ringing getting back a message 400 following is the cli

with extension based ring group it all works fine i just dont want to use em since it was causing crashes

any thoughts or work around?

-- Goto (from-outside-redir,+18885551212,15)
    -- Executing [+18885551212@from-outside-redir:15]
GotoIfTime("SIP/MTE1-b6e64430",
"*|*|*|*?from-outside-+18885551212-tl-allhours-TenantName|+18885551212|1")
in new stack
    -- Goto (from-outside-+18885551212-tl-allhours-TenantName,+18885551212,1)
    -- Executing [+18885551212@from-outside-+18885551212-tl-allhours-TenantName:1]
Set("SIP/MTE1-b6e64430", "__tenant=TenantName") in new stack
    -- Executing [+18885551212@from-outside-+18885551212-tl-allhours-TenantName:2]
Set("SIP/MTE1-b6e64430", "CDR(userfield)=TenantName") in new stack
    -- Executing [+18885551212@from-outside-+18885551212-tl-allhours-TenantName:3]
Set("SIP/MTE1-b6e64430", "MOH=VOsfira-TenantName") in new stack
    -- Executing [+18885551212@from-outside-+18885551212-tl-allhours-TenantName:4]
GotoIf("SIP/MTE1-b6e64430", "0?nomoh") in new stack
    -- Executing [+18885551212@from-outside-+18885551212-tl-allhours-TenantName:5]
SetMusicOnHold("SIP/MTE1-b6e64430", "VOsfira-TenantName") in new stack
    -- Executing [+18885551212@from-outside-+18885551212-tl-allhours-TenantName:6]
Macro("SIP/MTE1-b6e64430", "tl-huntlist|Operator-TenantName|") in new stack
    -- Executing [s@macro-tl-huntlist:1] Set("SIP/MTE1-b6e64430", "CALLERID(name)=Voore Inc") in new stack
    -- Executing [s@macro-tl-huntlist:2] Goto("SIP/MTE1-b6e64430",
"Operator-TenantName|s|1") in new stack
    -- Goto (Operator-TenantName,s,1)
  == Channel 'SIP/MTE1-b6e64430' jumping out of macro 'tl-huntlist'
    -- Executing [s@Operator-TenantName:1] NoOp("SIP/MTE1-b6e64430",
"Operator-TenantName") in new stack
    -- Executing [s@Operator-TenantName:2] Dial("SIP/MTE1-b6e64430", "SIP/203-TenantName&SIP/204-TenantName&SIP/205-TenantName&SIP/207-TenantName&SIP/209-TenantName&SIP/211-TenantName|30|i")
in new stack
    -- Called 203-TenantName
    -- Called 204-TenantName
    -- Called 205-TenantName
    -- Called 207-TenantName
    -- Called 209-TenantName
    -- Called 211-TenantName
    -- SIP/204-TenantName-08835018 is ringing
    -- SIP/MTE1-088134e8 is ringing
    -- SIP/203-TenantName-08bd0ab0 is ringing
    -- SIP/209-TenantName-0934fae8 is ringing
    -- Got SIP response 400 "Bad Request" back from 173.77.106.183
    -- SIP/204-TenantName-08835018 is circuit-busy  Extension
    -- Got SIP response 400 "Bad Request" back from 173.77.106.183
    -- SIP/205-TenantName-08a5eb58 is circuit-busy 
    -- Got SIP response 400 "Bad Request" back from 173.77.106.183
    -- SIP/207-TenantName-087345b8 is circuit-busy
    -- Got SIP response 400 "Bad Request" back from 173.77.106.183
    -- SIP/211-TenantName-08bdf938 is circuit-busy
    -- Got SIP response 400 "Bad Request" back from 173.77.106.183
    -- SIP/209-TenantName-0934fae8 is circuit-busy  ...
moshe

Fri, 04/30/2010 - 15:44 | the SIP response 400 is not

the SIP response 400 is not related to the phone status i get this message on extension while that were on the phone as well as extensions that ware not

Moshe

eeman

Sat, 05/01/2010 - 01:19 | i think its best to revert

i think its best to revert back to 3.2.2, 3.2.3 is so new i haven't had a chance to run it yet, but a google search indicates you arent alone in that error.

http://track.sipfoundry.org/browse/XTRN-1046

downgrading is as simple as upgrading, just unzip the file in the directory and your good to go.

Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com