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!

Voiceflex SIP Trunks with IPECS

Status
Not open for further replies.

ToffeeTom

Technical User
Nov 4, 2012
5
GB
Hi,

Anyone ever come across routing issues with Voiceflex SIP trunks on the LG EMG80? The trunks are registering via IP address Authentication

I have the trunks working of a fashion...I can dial out OK & calls are ringing in, the issue I am having is when I ring the DDI it appears to be ignoring what I have programmed in PGM 231 and ringing all live extensions!

I've set my lines in PGM 140 as DID
I've told it to use DID table in PGM 145

Any help would be great :)
 
Hi ToffeeTom

We have the same issue on an IPECS300. Now being asked to complete a wireshark trace. Did you get this resolved as we believe the provider is at fault not sending all the digits.



Ok, Press Trans *#..... TRANS/PGM..... the transfer key?.......sigh!
 
Are you using the SIP user ID table (PGM 126) for registration? Line 10 & 11 specify which method of DDI translation to use.

10 is "DID conversion"

11 should be " modify using flex DID conversion table"

 
Hi Thermus

The problem comes from the SIP provider as they can only send the full number which in turn defaults to the ring assignment on the system as PGM231 doesnt recognise the digits.. LG have come back saying to use the ICLID table to route incoming numbers based on the number dialled. It's a work around till we can get the provider to only send the digits we require.

Eats

Ok, Press Trans *#..... TRANS/PGM..... the transfer key?.......sigh!
 
Thermus

The ICLID part didnt work on site so a trace was taken and being sent to LG. Any more thoughts? The provider is definately send 12 digits (44 plus the full number without the leading zero).

Eats

Ok, Press Trans *#..... TRANS/PGM..... the transfer key?.......sigh!
 
Have you tried to use the routing via User ID, then it should be no problem
when the provider sends a 12 digit number?

for example:
-I get 541244484455555 from the provider
-create in PGM126 for every number an own index
-set Ring Route Type=ID assigned station
-assign this index to the station in the station atributes

But it can be a lot of work...

 
Hi all

I have MFIM50 and UCP100 both working with voiceflex using registrar I am now going to set up eMG80 so I will update you with the results
 
All

Update.... Our IPECS is now working fine with incoming DDI's. Its a very messy scenario but does work.

The problem I had was all of my DDI's were failing to the main DDI. After tracing and deciphering a trace it appeared that the provider was not sending the DDI as you would normally expect.

The provider was always sending the 'URI' which was always the main bearer number followed by the 'To ID' which was the number dialled. Most, if not all, providers can change this to accomodate the system. No names given, but if you come across this issue you can rectify it without spending hours on site questioning yourself!!!!!

The IPECS is defaulted to always look at the URI field first so we had to go to PGM 133, scroll down to Caller/Called ID Option, Called ID, and change the field from 'Request URI' to 'To ID'.

Now this still gave us a headache as we couldnt strip down the DDi's to 3 digits so we had to use 'System Call Routing' PGM251. We had to fill in the 'Called Number' field the full digits being sent. Then we still had to use PGM231 and set the DDI's up with names so that the name displayed on the handset.

It is messy but works, hopefully you have a provider that can assist rather than hinder!

Eats.

Ok, Press Trans *#..... TRANS/PGM..... the transfer key?.......sigh!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top