Who Me Too'd this topic

Ian Darby · ‎05-28-2012

Hi,

We have recently upgraded our TMS to 13.2 and we are running X7.1 on our VCSC & VCSE. We configured the new Provisioning Extension and synchronised all of the services between TMS-VCS OK.

When we attempted to configure Jabber 4.3 clients within the PE on TMS, we could not call between any Jabber clients internally. Calls between Jabber clients and other room-based C20, 1700 systems worked OK, and calls externally worked fine as well.

When calling between Jabber clients internally, Jabber just kept coming up with a call fail error.

Search history from the VCSC below:

Search (224)
- State: Completed
- Found: False
- Reason: Forbidden
- Type: SIP (INVITE)
- CallSerial Number: 156afcb6-a922-11e1-ad32-0010f30f59e4
- Tag: 156afdec-a922-11e1-a40a-0010f30f59e4
- StartTime: 2012-05-29 12:06:05
- Duration: 0.01
- Source (1)
- - Authenticated: True
- - Aliases (1)
  - - Alias (1)
    - - Type: Url
    - - Origin: Unknown
    - - Value: Richard.Bullock@vcs.agile.co.nz
- - Zone (1)
  - - Name: LocalZone
  - - Type: Local
- - Path (1)
  - - Hop (1)
    - - Address: 172.17.17.108:54148
- Destination (1)
- - Alias (1)
  - - Type: Url
  - - Origin: Unknown
  - - Value: sip:Ian.Darby@vcs.agile.co.nz
- SubSearch (1)
- - Type: Transforms
- - Action: Not Transformed
- - ResultAlias (1)
  - - Type: Url
  - - Origin: Unknown
  - - Value: Ian.Darby@vcs.agile.co.nz
- - SubSearch (1)
  - - Type: Admin Policy
    - Action: Proxy
  - - ResultAlias (1)
    - - Type: Url
    - - Origin: Unknown
    - - Value: Ian.Darby@vcs.agile.co.nz
  - - SubSearch (1)
    - - Type: FindMe
    - - Action: Reject

Has anyone else experienced this problem, or could point us towards a solution to this?

We have had to revert back to the Legacy TMS Agent to get everything runnning again.

Thanks.

Who Me Too'd this topic

VCS Provisioning Extension Jabber 4.3 calling problem